[Bug 11468] spec logic: replaceState before onload should not affect onload object or popstate should not fire after onload.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11468

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WORKSFORME

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-12-13 23:17:24 UTC ---
Example[2] is fixed in the spec now; the popstate would include the
pushState()d data.

Example[1] is working as intended. Just make the page load minimal, immediately
replaceState() and then load the page from the popstate event. (You can include
all the data in the initial connection so that the latency is no worse.)
Alternatively, keep track of what the current state is and just don't do
anything if reloading the current state (and use replaceState() when the page
loads to track what the first state is).

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: Partially Accepted
Change Description: no spec change
Rationale: See above.

-- 
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 Monday, 13 December 2010 23:17:34 UTC