http://www.w3.org/Bugs/Public/show_bug.cgi?id=8837 Summary: Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec bugs AssignedTo: dave.null@w3.org ReportedBy: hsivonen@iki.fi QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org When the creation of a browsing context doesn't start a navigation to another URL, the DOMFrameContentLoaded and load events should fire (asynchronously) for the initial about:blank document. Failing to fire these events broke enough test cases and deviates from current browser practice so that I didn't bother to gather evidence about breaking the Web, but it seems reasonable to expect the failure to fire these events to break the Web. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.Received on Friday, 29 January 2010 12:38:00 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC