Opened 10 years ago
Closed 10 years ago
#12674 closed Bug (duplicate)
iframe fallback contents encoded
Reported by: | UserAccount1 | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | |
Keywords: | Cc: |
Description
I think I've found a bug when adding iframe fallback content.
If I enter the below into the source.
<iframe src="http://google.co.uk" > TEST FALL BACK CONTENT <a href="#">this is a link</a> </iframe> The fallback content is being encoded, and from what I can see from W3C this should not happen.
<iframe src="http://google.co.uk">TEST FALL BACK CONTENT &amp;amp;lt;a data-cke-saved-href=&amp;quot;#&amp;quot; href=&amp;quot;#&amp;quot;&amp;amp;gt;this is a link&amp;amp;lt;/a&amp;amp;gt;</iframe>
Change History (1)
comment:1 Changed 10 years ago by
Component: | Accessibility → General |
---|---|
Keywords: | iframe fallback encoding removed |
Resolution: | → duplicate |
Status: | new → closed |
DUP of #11442.
BTW. Check out this comment: http://dev.ckeditor.com/ticket/11442#comment:6
And (source: http://dev.w3.org/html5/spec-preview/the-iframe-element.html):
Basically it doesn't make sense any more to provide the fallback content and it's parsed by the browsers as a text, what causes the issue that you reported.