Ticket #2522 (closed Bug: invalid)

Opened 6 years ago

Last modified 2 years ago

Bug report: no empty value on firefox

Reported by: Almog Owned by:
Priority: Normal Milestone:
Component: Core : Output Data Version: FCKeditor 2.6.4
Keywords: HasPatch Cc:

Description

I used on the last ver of the fckeditor(Night build), and when i set the value to ""[empty] on firefox the value become to "<br>".

This bug makes some problems, start by the empty checking(& I have to "igonore" it by php) and continue to char counting.

I hope to find an any solution.

Best regards, Almog Baku,

Israel

Attachments

2522.patch (546 bytes) - added by botimer 5 years ago.
Patch to handle dangling BR tags

Change History

comment:1 Changed 6 years ago by alfonsoml

  • Priority changed from High to Normal
  • Keywords break line, <br? removed

comment:2 Changed 6 years ago by arczi

  • Keywords Pending WorksForMe added
  • Summary changed from Bug report: NO EMPTY VALUE ON FIREFOX to Bug report: no empty value on firefox

Could you try reproduce it with current Night build? How you set an empty value?

Changed 5 years ago by botimer

Patch to handle dangling BR tags

comment:3 Changed 5 years ago by botimer

  • Keywords Confirmed HasPatch added; Pending WorksForMe removed
  • Version set to FCKeditor 2.6.4

Attached is a patch to FCKXHtml._AppendNode(). It ensures that, when EnterMode = br, the padding node is not returned by FCK.GetXHTML(). This fixes two specific symptoms:

  1. Editors with no content in WYSIWYG mode are submitted with a single BR tag
  2. FCK.GetXHTML() is dirtying the content by tracking the padding node improperly

This is also related to ticket #1150. The attached patch does not resolve the issue where Select All followed by a backspace while EnterMode = br leaves a dangling BR that is not the padding node.

This scenario can be exercised with Sample 12. Steps to test:

  1. Select EnterMode = br.
  2. Select Source mode
  3. Remove all content
  4. Return to WYSIWYG mode
  5. Click Submit

With this patch, there should be no submitted content on the result page. Without it, there will be a stray <br />, which has been stripped of the bogus node attributes (as a result of #1150 / [2219]).

comment:4 Changed 2 years ago by j.swiderski

  • Status changed from confirmed to closed
  • Resolution set to invalid

FCKeditor was retired and is no longer supported. All active development was moved to its successor, CKEditor 3.x, that is a fully mature and far superior product. We recommend you upgrade as soon as possible.

Note: See TracTickets for help on using tickets.
© 2003 – 2012 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy