W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2010

[Bug 8782] reinvestigate what parts of session history should be sync and what parts should be async

From: <bugzilla@wiggum.w3.org>
Date: Tue, 19 Jan 2010 06:56:04 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NX80S-00061m-9Y@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8782





--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-19 06:56:03 ---
I have some tests for this here:

   http://www.hixie.ch/tests/adhoc/dom/level0/history/sync-vs-async/

...but other tests would be great.

Things to look at include:

 * how should script authors know what onhashchange fired for if there's no
state in the event, if it's async, and if the user clicked "back" twice
quickly?

 * how should history.back() inside onpopstate/onhashchange work?


-- 
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 Tuesday, 19 January 2010 06:56:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC