Opened 16 years ago
Closed 16 years ago
#2355 closed Bug (fixed)
FCK:editor output is not XHTML 1.0 compliant
| Reported by: | Michael Osipov | Owned by: | Michael Osipov |
|---|---|---|---|
| Priority: | Must have (possibly next milestone) | Milestone: | FCKeditor.Java 2.4.1 |
| Component: | Server : Java | Version: | FCKeditor.Java 2.4 |
| Keywords: | Cc: |
Description
the produced iframe source fails W3C validation.
Change History (8)
comment:1 Changed 16 years ago by
| Milestone: | → FCKeditor.Java 2.5 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:2 Changed 16 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
The W3C specification defines that & must be used, not &. That's what we have in all other languages btw.
See: C.12. Using Ampersands in Attribute Values (and Elsewhere) in the XHTML 1.0 specs.
comment:3 Changed 16 years ago by
& == & The spec does only say that you have to escape the ampersand. That's what I did. The code is perfectly valid. There is no regulation saying you have to use the name instead of the unicode point. I ran my code thru the W3C validator and it's valid.
comment:4 Changed 16 years ago by
I'm not strictly defend one or another implementation. I'm just pointing that the Java implementation is different from all other languages, with no apparent reason.
comment:5 Changed 16 years ago by
| Owner: | set to Michael Osipov |
|---|---|
| Resolution: | → fixed |
| Status: | reopened → closed |
Fixed in [2224] for the sake of uniformity.
comment:6 Changed 16 years ago by
| Milestone: | FCKeditor.Java 2.5 → FCKeditor.Java 2.4.1 |
|---|
comment:7 Changed 16 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Merge patch to branch 2.4.x
comment:8 Changed 16 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Branch 2.4.x merged with trunk in [2537]
Fixed with [2210]