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

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

--- Comment #4 from Max Kanat-Alexander <mkanat@bugzilla.org> 2011-04-08 03:35:24 UTC ---
  Oh, that's fine about the terseness, I wasn't offended or anything. :-)

(In reply to comment #3)
>  Since the parameter currently does nothing, suddenly causing it to affect the
> DOM could create bugs in sites.

  True, although it will affect fewer sites if we change it now than it will in
the future.

> I don't think that pushState updating document.title adds a large amount of
> convenience for web developers,

  Well, it could in very complex situations. Essentially, if authors start
doing a lot of pushState that we *want* to affect the title (say, implementing
an entire multi-page application), then you're pushing the burden of that
document.title complexity onto us instead of into the browser. That is, if
somebody does start using this API in a very involved application, the problems
you're talking about are going to have to be resolved anyway, and it's going to
be even more difficult to resolve them in the application than to resolve them
in the browser. (Or even if it's simpler, it's going to be a lot of duplication
of effort across web applications.)

> 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!

  Oh, that's true too. What would be valuable to do with it otherwise?

-- 
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 03:35:26 UTC