Closed
Bug 544535
Opened 15 years ago
Closed 15 years ago
Ignore push/replaceState's title argument
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: justin.lebar+bug, Assigned: justin.lebar+bug)
References
Details
Attachments
(1 file)
3.49 KB,
patch
|
sicking
:
review+
benjamin
:
approval2.0+
|
Details | Diff | Splinter Review |
Our current implementation of the title argument in history.push/replaceState is unsatisfactory.
Currently, calling |history.replaceState(null, "foo");| changes the session history entry's title (seen when you press the down arrow next to the forward button) to "foo". But when the page is re-visited (e.g. the user goes back then forward), its shentry's title is set back to the value in document.title.
If there is a title parameter, it should probably be persisted in the shentry. The way this would work, I think, is that changes to document.title would be reflected in the shentry's title, as they are now, unless the shentry was created by a pushState or modified by a replaceState. In that case, changes to document.title don't affect the shentry's title; the shentry's title can only be changed by calling replaceState.
I've argued on whatwg [1] that we should get rid of the title parameter from push/replaceState altogether, because I think the solution above adds a lot of complication for very little gain. My arguments didn't get much traction at the time, however.
I think we should either push to get the title parameter removed from pushState, implement the above strategy for persisting shentry titles, or come up with an alternative strategy.
[1]: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-November/024138.html
Assignee | ||
Comment 1•15 years ago
|
||
Pinging Jonas and Smaug on this issue. I think we need to resolve this one way or another before we start seriously evangelizing pushState.
Assignee | ||
Comment 2•15 years ago
|
||
Perhaps we should start ignoring the title argument to establish parity with what WebKit currently does? We can always change it later to reflect our proposal to WhatWG that the pushState title affect document.title.
That sounds good to me. I'd even be ok with implementing our proposal, both to show we are serious, and to gather implementation experience.
Assignee | ||
Comment 4•15 years ago
|
||
Easy patch to ignore the title parameter, if we want to take it.
Assignee: nobody → justin.lebar+bug
Status: NEW → ASSIGNED
Attachment #457130 -
Flags: review?(jonas)
Attachment #457130 -
Flags: review?(jonas) → review+
Assignee | ||
Comment 5•15 years ago
|
||
Comment on attachment 457130 [details] [diff] [review]
Patch to ignore the title
Jonas and I think we should check this in now. We can always hook the title parameter up to document.title later.
Attachment #457130 -
Flags: approval2.0?
Updated•15 years ago
|
Attachment #457130 -
Flags: approval2.0? → approval2.0+
Assignee | ||
Updated•15 years ago
|
Summary: Fix title argument implementation in history.push/replaceState → Ignore push/replaceState's title argument
Assignee | ||
Comment 6•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
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
•