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 #11442, comment 6

Timestamp:: Feb 5, 2014, 10:52:06 PM (11 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11442, comment 6

-                      v1
+                      v2
 > The HTML parser treats markup inside iframe elements as text.
+However, this doesn't explain how CKEditor should handle the situation. I would say that it should follow the spec, although this is low prio ticket because setting iframe's content to anything is basically deprecated and useless.
+However, this doesn't explain how CKEditor should handle the situation. I would say that it cannot follow the spec, because:
+. You load <iframe>f<!--x-->x</iframe>
+. It becomes <iframe>f&lt;--x--&gt;x</iframe>
+. You load this and it becomes <iframe>f&amp;lt;--x--&amp;gt;x</iframe>
+So CKEditor should preserve the original content... or strip everything more than text. Both solutions are not easy and since setting content of an iframe is deprecated because useless, this ticket has low priority.