This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7232 - add <iframe> to list of CDATA elements in the "Writing HTML documents" section
Summary: add <iframe> to list of CDATA elements in the "Writing HTML documents" section
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2009-08-06 09:58 UTC by Michael[tm] Smith
Modified: 2010-10-04 14:48 UTC (History)
3 users (show)

See Also:


Description Michael[tm] Smith 2009-08-06 09:58:47 UTC
The "Tree construction" section requires that <iframe> elements be parsed as CDATA elements, so the list of CDATA elements in the "Writing HTML documents" section should include <iframe>.
Comment 1 Ian 'Hixie' Hickson 2009-08-08 01:05:00 UTC
No, <iframe> isn't CDATA for syntax purposes, only for parsing. From a syntax point of view, it's more like <noscript>:

"When used in HTML documents, the allowed content model of iframe elements is text, except that invoking the HTML fragment parsing algorithm with the iframe element as the context element and the text contents as the input must result in a list of nodes that are all phrasing content, with no parse errors having occurred, with no script elements being anywhere in the list or as descendants of elements in the list, and with all the elements in the list (including their descendants) being themselves conforming."
Comment 2 Maciej Stachowiak 2010-03-14 14:48:50 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.