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 17244 - "When an iframe element is first inserted into a document, the user agent must create a nested browsing context, and then process the iframe attributes for the first time." - this is very confusing. The "process the iframe attributes" steps have to be run
Summary: "When an iframe element is first inserted into a document, the user agent mus...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-30 08:03 UTC by contributor
Modified: 2012-07-18 18:48 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-05-30 08:03:31 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-iframe-element
Complete: http://www.whatwg.org/c#the-iframe-element

Comment:
"When an iframe element is first inserted into a document, the user agent must
create a nested browsing context, and then process the iframe attributes for
the first time." - this is very confusing. The "process the iframe attributes"
steps have to be run *each* time that an iframe is inserted into the document. 

Posted from: 2001:4c28:a030:30:ecfa:bf5f:96ca:7bec
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.10.289 Version/12.00
Comment 2 Ian 'Hixie' Hickson 2012-05-30 23:14:21 UTC 
The spec currently doesn't get rid of the browsing context when you remove the element, so no, it's intended that it only run the first time.

This will likely change, so I'm leaving this open for now and will fix it once we change when he browsing contexts go away.