28772 2015-06-06 04:36:12 +0000 fired unload flag never gets set back to false for document.open 2016-04-21 22:29:24 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#unloading-documents P3 normal Unsorted 1 contributor ian annevk bzbarsky d mike contributor oldest_to_newest 120759 0 contributor 2015-06-06 04:36:12 +0000 Specification: https://html.spec.whatwg.org/multipage/browsers.html Multipage: https://html.spec.whatwg.org/multipage/#unloading-documents Complete: https://html.spec.whatwg.org/#unloading-documents Referrer: Comment: fired unload flag never gets set back to false for document.open 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 120760 1 bzbarsky 2015-06-06 04:38:27 +0000 https://html.spec.whatwg.org/multipage/webappapis.html#opening-the-input-stream step 10 says to do https://html.spec.whatwg.org/multipage/browsers.html#unload-a-document which will fire unload and set the "fired unload flag" to true. But if the document is later unloaded (e.g. by a navigation) that means it won't fire unload at that time, no? Seems to me like the steps for document.open (or document unloading when the recycle flag is set?) should set this boolean back to false somewhere. 125606 2 annevk 2016-03-23 13:35:27 +0000 So, introduce a new step before "Unload event" that says "If /recycle/ is true, set the Document's fired unload flag to false."? I'm a little bit out of my debt here, but happy to fix this. (The "if any event listeners were triggered" condition is also interesting. That's a primitive the DOM Standard does not really offer at the moment.) 126038 3 d 2016-04-21 22:29:24 +0000 https://github.com/whatwg/html/pull/1018