Ticket #114 (closed Bug: fixed)

Opened 8 years ago

Last modified 7 years 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 (623 bytes) - added by joelwreed@… 8 years ago.
patch

Change History

Changed 8 years ago by joelwreed@…

patch

comment:1 in reply to: ↑ description Changed 7 years 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?

comment:2 Changed 7 years ago by fredck

  • Milestone changed from FCKeditor 2.4 to FCKeditor 2.4.1
Note: See TracTickets for help on using tickets.
© 2003 – 2012 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy