Closed
Bug 535999
Opened 15 years ago
Closed 14 years ago
Figure out what history.pushState should do when it's called early in the page's lifecycle
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 615501
People
(Reporter: justin.lebar+bug, Unassigned)
References
Details
What happens if history.pushState is called very early in a page's lifecycle? Is it possible to call pushState before we've created a history entry for the current page? In that case, it would be tricky to link the new history entry to the current one.
(See also comments 33 and 34 in bug 500328.)
|
Reporter | |
Comment 1•14 years ago
|
||
See also the last paragraph in http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/028241.html
|
|
Reporter | |
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
|
Assignee | |
Updated•12 years ago
|
Component: DOM: Other → DOM
|
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•