- From: <bugzilla@jessica.w3.org>
- Date: Fri, 12 Aug 2011 20:19:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13462 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |FIXED --- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-12 20:19:01 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. I've made document.open() force salvageable to false while the unloading happens, then force it back to true for the "new" document. In the case of history navigation, the timeouts are suspended because the algorithm for setTimeout and setInterval requires the time to be time spent with the document fully active. For example, step 7 of the setTimeout algorithm says "...wait until the Document associated with the method context has been fully active for a further timeout milliseconds (not necessarily consecutively).". Please don't hesitate to reopen the bug if I've missed something here. -- 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, 12 August 2011 20:19:07 UTC