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

Changes between Version 1 and Version 2 of Ticket #7543, comment 7

Timestamp:: Sep 18, 2012, 9:57:27 PM (13 years ago)
Author:: Les Orchard
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #7543, comment 7

-                      v1
+                      v2
 I pasted the code that shows the issue, using just htmlParser and htmlWriter from CKEditor. Like I said, as far as I can tell, it's parsing my markup without using the browser's parser.
 > Having said all that, where is CKEditor fault? Could you show or explain it to me?
+I already showed it to you.
+I already showed it to you, in the example code using htmlParser and htmlWriter.
 As far as I'm concerned, as a user of the CKEditor code: Some not-great markup gets made even less great. I'd like to stop it from doing that. Clearly you don't see it as a problem, so I'm left to try fixing it myself. Understood, thanks.