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 History
Next Change →

Changes between Initial Version and Version 2 of Ticket #10073

Timestamp:: Feb 14, 2013, 2:24:11 PM (11 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #10073
- Property Status changed from new to confirmed

Ticket #10073 – Description

initial	v2
12	12	* {{{<a href=""><img></a>}}} is a different case because it's similar to {{{<a name=""><img></a>}}} and {{{<a name=""></a>}}} shouldn't be removed. So it's an exception, because 'a' isn't included in {{{$removeEmpty}}}. However, why doesn't data processor fix this case? It fixes the case I described in the next point, but why not this? Especially, that I see a filter's rule for htmlFilter that fixes this on output. I think that identical rule should exist for toHtml(). And perhaps previous point should also be handled by data processor...
13	13	* {{{<p><img></p>}}}}: after filtering out {{{<img>}}} filter will left empty {{{<p></p>}}} which then will be correctly handled by data processor, so in this case we don't have to act.
	14
	15	Important note: http://dev.ckeditor.com/ticket/9992#comment:7