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

[Bug 12447] history.pushState / replaceState's title parameter is unsatisfactory

From: <bugzilla@jessica.w3.org>
Date: Fri, 08 Apr 2011 02:02:17 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q811d-0000Lm-SO@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12447

--- Comment #3 from Justin Lebar <justin.lebar@gmail.com> 2011-04-08 02:02:16 UTC ---
> I don't, but I figure as a bug reporter my job is to accurately describe the
> problem, and that the spec authors would be the people with the broad
> experience required in order to make judgments about implementation.

I'm sorry if I came across as terse.  I just wanted your input, if you had any.

At this point, I don't think we can link the title parameter to document.title.
 Since the parameter currently does nothing, suddenly causing it to affect the
DOM could create bugs in sites.

I'm also not sure how to sanely link the title parameter up to document.title. 
It gets really complicated when you start thinking about what happens when you
go back and forward; you need to update document.title on each navigation, but
some session history entries need to their saved titles from others...

I don't think that pushState updating document.title adds a large amount of
convenience for web developers, so the main benefit of mucking around here
would be to make the API a little more sane.  But at that point, we're not tied
to making the second parameter affect the page's title; we could make it do
anything!

-- 
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 Friday, 8 April 2011 02:02:19 UTC

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