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 10522 - Consider making iframe, noframes or noembed as the ancestor of a script prevent execution
Summary: Consider making iframe, noframes or noembed as the ancestor of a script preve...
Status: CLOSED WONTFIX
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-01 12:36 UTC by Henri Sivonen
Modified: 2010-10-04 14:48 UTC (History)
4 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-09-01 12:36:20 UTC 
When running a script, Gecko checks if the script has an iframe, noframes or noembed (in the HTML namespace) ancestor. If there is one, the script is marked as already started and the running steps are terminated.

Please consider adding this to the spec.
Comment 1 Ian 'Hixie' Hickson 2010-09-25 19:37:21 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: 

I actually did consider this while designing this part of the spec.

It would only matter for XHTML. XHTML content is not allowed to have descendants of <iframe>, and <noframes> and <noembed> are non-conforming anywhere, especially in XHTML where they have no effect on anything else either. 

I don't see much value therefore in adding code to handle this particular case, since it would only affect non-conforming XHTML content using obsolete features that never worked reliably in XML anyway, and it would still not solve the multitude of other similar issues with those elements (such as form controls still submitting, etc).
Comment 2 Henri Sivonen 2010-09-28 11:10:28 UTC 
OK. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=600175