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 28773 - Nothing ever sets the "mute iframe load" flag to false
Summary: Nothing ever sets the "mute iframe load" flag to false
Status: RESOLVED MOVED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#the-ifr...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-06 05:21 UTC by contributor
Modified: 2019-03-29 20:24 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2015-06-06 05:21:08 UTC 
Specification: https://html.spec.whatwg.org/
Multipage: https://html.spec.whatwg.org/multipage/#the-iframe-element
Complete: https://html.spec.whatwg.org/#the-iframe-element
Referrer: 

Comment:
Nothing ever sets the "mute iframe load" flag to false

Posted from: 98.110.194.132
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Firefox/41.0
Comment 1 Boris Zbarsky 2015-06-06 05:22:56 UTC 
If a load event on an <iframe> does document.open() on the document inside that iframe, the spec sets the "mute iframe load" flag on that document.  That means that close() on the document will never fire the load event on that iframe, ever.  Not even if there are lots of open()/close() pairs that come from places other than the iframe's load event.

This seems a bit odd to me....
Comment 2 Domenic Denicola 2019-03-29 20:24:17 UTC 
https://github.com/whatwg/html/issues/4292