[Bug 17231] It seems that it isn't possible to create a second load event by doing a document.open/document.write/document.close sequence from within an existing load event

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17231

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi

--- Comment #5 from Henri Sivonen <hsivonen@iki.fi> 2012-06-04 09:45:37 UTC ---
(In reply to comment #4)
> Does any of the other logic happen? What does document.readyState switch to? Do
> scripts run the way they do with a network parser? (e.g. does defer="" delay
> until document.close()?) Does DOMContentLoaded fire again? pageshow? Do
> appcache things get delayed again? Does window.print() get delayed again
> between open() and close()?

Per
http://hsivonen.iki.fi/test/moz/readystate/document-open.html
I expect document.open() to switch readyState back to "loading" and
DOMContentLoaded to fire when the stream has been exhausted. It seems that the
"load" event fires also as well as, in Gecko, "pageshow".

By code inspection, I would expect app cache selection to run again and defer
scripts to be deferred again.

There should already be feedback about this in your pending mailboxes that
store WHATWG e-mail.

-- 
Configure bugmail: https://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 Monday, 4 June 2012 09:47:59 UTC