CKEditor does not work in IE 7/8 for textareas containing a bullet character · in the ID

[Inigo]

The bullet character · is legal in HTML ids, but when CKeditor attempts to turn a textarea with a bullet in the id into a rich text editor, then the text content comes out as "undefined" in IE.

e.g.

<textarea class="richtext" id="xf-411·1-2">some content</textarea>

when turned into a rich text editor via CKEDITOR.replace, works fine in Firefox 3.5 and Chrome (Windows), but in IE 7 and 8 it displays the text "undefined" rather than "some content".

This is not a theoretical problem - generated content from libraries like Orbeon uses the bullet character extensively in IDs, and this prevents CKeditor 3.0.1 from being used with them.

Tested with 3.0.1 on Windows XP, with IE 8.0.6001.18702 and in IE 7 compatibility mode.

[Garry Yao]

Quote from XHTML1.0 Spec:

Note that the collection of legal values in ​XML 1.0 Section 2.3, production 5 is much larger than that permitted to be used in the ID and NAME types defined in HTML 4. When defining fragment identifiers to be backward-compatible, only strings matching the pattern [A-Za-z][A-Za-z0-9:_.-]* should be used. See ​Section 6.2 of HTML4 for more information.

[Inigo]

I don't understand your point - the section of spec you are quoting is explicitly saying that XHTML supports a wide range of characters in IDs. The referenced XML 1.0 Section 2.3 defines IDs as:

NameStartChar ::= ":" | [A-Z] | "_" | [a-z] | #xC0-#xD6 | #xD8-#xF6 | #xF8-#x2FF | #x370-#x37D | #x37F-#x1FFF | #x200C-#x200D | #x2070-#x218F | #x2C00-#x2FEF | #x3001-#xD7FF | #xF900-#xFDCF | #xFDF0-#xFFFD | #x10000-#xEFFFF

NameChar ::= NameStartChar | "-" | "." | [0-9] | #xB7 | #x0300-#x036F | #x203F-#x2040

so middle dot (#xB7) is valid in XHTML (except as the first character). (Note also that it appears to be valid in the HTML 5 spec - as far as I can tell, pretty much any non-space character is valid in an ID in HTML 5).

I'm not using HTML 4, and I have no interest in compatibility with HTML 4. I expected CKeditor to be able to work with valid XHTML and valid HTML 5, rather than just being an HTML 4 editor.

[Frederico Caldeira Knabben]

If it's XHTML, we should support it. Targeting to the 3.2 for investigation, hoping this is not a browser issue.

[Alfonso Martínez de Lizarrondo]

Works for me in both the replaceByClass and replaceByCode examples.

Can you verify with the 3.1 release?

[Minh Nguyen]

Works for me in current trunk, please feel free to reopen the ticket at any time.