W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13498] document.readyState should return to 'loading' on navigation

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Aug 2011 01:09:44 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QqxIm-0005yX-N9@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
                 CC|                            |ian@hixie.ch

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-10 01:09:44 UTC ---
Hrm, that's kind of a pain. Do they switch it back to 'complete' if the load
ends up being a download or ends up canceled or whatnot? Where does this happen
relative to the onbeforeunload handler? How about relative to parser abortion
in the case the readyState was still not 'complete'? How does this interact
with history navigation? (e.g. if you go back to the document and it was
bfcached, does it still have this new state or does it go back?)

Do other browsers do this also?

Are there any tests for this?

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 Wednesday, 10 August 2011 01:09:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:16 UTC