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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Jan 2011 19:05:05 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PcjWj-0002fI-Qz@jessica.w3.org>

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

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-11 19:05:05 UTC ---
If we fired the initial popstate onload, then the page would essentially
"regress" at load if the user caused there to be pushstates before the load,
unless we kept track of all the states and popped through the in sequence, but
that would likely conflict with whatever code was calling pushState() in the
first place. If we just didn't delay the popstate event, then going back in
history from another page to a page that already had state data would cause the
state data to be lost as the popstate would fire before the scripts to handle

> How minimal?

Minimal enough that there's no UI to interact with before onload fires.

Your problems all seem to be predicated on the idea that the page will appear
usable (but not be) for a long time before the load event fires. You don't want
to do that. If you need to wait for the 'load' event (which you do if you're
using pushState/popstate) then construct your page so that only critical
resources load before the load event, then have the load event set up the page,
and then kick off non-critical resource loads.

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:

Status: Rejected
Change Description: no spec change
Rationale: this is working as intended.

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, 11 January 2011 19:05:07 UTC

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