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 2 and Version 3 of Ticket #7543, comment 7

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

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #7543, comment 7

-                      v2
+                      v3
 > >>As far as I can tell, the parser and writer in CKEditor don't use the browser's parsing facilities.
 > Yeah, sure CKEditor gets to the code before browser does. Good one.[[BR]]
+I'm guessing that, yes, it does that when I:
+. Click "source"
+. Paste the markup into the textarea
+. Click "source" again
 > Of course CKEditor doesn't use browser parsing facilities but it gets HTML processed by a browser  and browser is the one that destroys your code first **not CKEditor**.