[whatwg] <a onlyreplace>
jonas at sicking.cc
Sat Oct 17 23:47:37 PDT 2009
On Sat, Oct 17, 2009 at 12:45 PM, Nelson Menezes
<flying.mushroom at gmail.com> wrote:
> 2009/10/17 Jonas Sicking <jonas at sicking.cc>:
>> In fact, you don't even need to use pushState. For now this can be
>> faked using onhashchange and fragment identifier tricks. It's
>> certainly not as elegant as pushState (that is, after all, why
>> pushState was added), but it's something that can be tried today.
> Well, here's a badly-hacked-together solution that emulates this behaviour...
> I think it'll be helpful even if it only gets used in a JS library as
> you mention (change the attribute to a classname then). Still, it can
> be made to work with today's browsers:
Yay, sweet! But why so much cruft in the hash? Also, going back to the
original page (where there is no hash) doesn't seem to work (at least
in Firefox trunk nightlies).
More information about the whatwg