Opened 9 years ago

Closed 9 years ago

#12674 closed Bug (duplicate)

iframe fallback contents encoded

Reported by: UserAccount1 Owned by:
Priority: Normal Milestone:
Component: General Version:
Keywords: Cc:


I think I've found a bug when adding iframe fallback content.

If I enter the below into the source.

<iframe src="" > 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="">TEST FALL BACK CONTENT &amp;amp;amp;lt;a data-cke-saved-href=&amp;amp;quot;#&amp;amp;quot; href=&amp;amp;quot;#&amp;amp;quot;&amp;amp;amp;gt;this is a link&amp;amp;amp;lt;/a&amp;amp;amp;gt;</iframe>

Change History (1)

comment:1 Changed 9 years ago by Piotrek Koszuliński

Component: AccessibilityGeneral
Keywords: iframe fallback encoding removed
Resolution: duplicate
Status: newclosed

DUP of #11442.

BTW. Check out this comment:

And (source:

Descendants of iframe elements represent nothing. (In legacy user agents that do not support iframe elements, the contents would be parsed as markup that could act as fallback content.)

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.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy