#114 closed Bug (fixed)
Respect FCKConfig.ProcessHTMLEntities when FCKConfig.FillEmptyBlocks is enabled
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | Normal | Milestone: | FCKeditor 2.4.1 |
| Component: | General | Version: | FCKeditor 2.4 |
| Keywords: | Cc: |
Description
In the 2.4 version of editor/_source/internals/fckxhtml.js when FCKConfig.FillEmptyBlocks is enabled, the _AppendChildNodes function will insert in empty blocks. HOWEVER, when FCKConfig.ProcessHTMLEntities is false we should insert #160 instead.
The insertion of will generate invalid XHTML, whereas using   will generate valid XHTML.
A patch has been attached.
Attachments (1)
Change History (3)
Changed 19 years ago by
| Attachment: | ticket-114.patch added |
|---|
comment:1 Changed 19 years ago by
| Keywords: | nbsp ProcessHTMLEntities FillEmptyBlocks removed |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Replying to joelwreed@gmail.com:
In the 2.4 version of editor/_source/internals/fckxhtml.js when FCKConfig.FillEmptyBlocks is enabled, the _AppendChildNodes function will insert in empty blocks. HOWEVER, when FCKConfig.ProcessHTMLEntities is false we should insert #160 instead.
Your assumption is correct, as this is the way we do to preserve subsequent white spaces.
Fixed with [167].
The insertion of will generate invalid XHTML, whereas using   will generate valid XHTML.
I'm not sure about it: http://www.w3.org/TR/xhtml1/dtds.html#a_dtd_XHTML-1.0-Strict#H-A2
Wasn't you talking about XML?
comment:2 Changed 19 years ago by
| Milestone: | FCKeditor 2.4 → FCKeditor 2.4.1 |
|---|
patch