Ticket #114 (closed Bug: fixed)

Opened 22 months ago

Last modified 21 months ago

Respect FCKConfig.ProcessHTMLEntities when FCKConfig.FillEmptyBlocks is enabled

Reported by: joelwreed@… 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 &#160 will generate valid XHTML.

A patch has been attached.

Attachments

ticket-114.patch (0.6 KB) - added by joelwreed@… 22 months ago.
patch

Change History

Changed 22 months ago by joelwreed@…

patch

in reply to: ↑ description   Changed 21 months ago by fredck

  • keywords nbsp ProcessHTMLEntities FillEmptyBlocks removed
  • status changed from new to closed
  • resolution set to fixed

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 &#160 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?

  Changed 21 months ago by fredck

  • milestone changed from FCKeditor 2.4 to FCKeditor 2.4.1
Note: See TracTickets for help on using tickets.