We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #10601, comment 4

Timestamp:: Sep 2, 2013, 11:19:53 AM (11 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #10601, comment 4

initial	v1
1		Actually, I'm wrong, because I was thinking about the issue that causes this one. The original issue, reported on Bugzilla, is that FF inserts bogus <br> after data are set. Of course, if that issue was fixed by the FF team, it would also fix this one (which is related to data processing), but we I believe that we can try to find a solution inside the data processor to at least have data clean.
	1	Actually, I'm wrong, because I was thinking about the issue that causes this one. The original issue, which reported on Bugzilla, is that FF inserts bogus <br> after data is set. Of course, if that issue was fixed by the Mozilla team, it would also fix this one (which is related to processing HTML broken by FF), but I believe that we can try to find a solution inside the data processor to at least have clean output data.