W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] setting location.hash property and browser reload

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 08 Jul 2009 23:29:02 -0700
Message-ID: <4A558E2E.6050803@mit.edu>
Ian Hickson wrote:
> HTML5 requires that there not be a reload. Setting location.hash 
> eventually (if you follow the admittedly convoluted definitions) is 
> equivalent to running the navigation algorithm:
>    http://www.whatwg.org/specs/web-apps/current-work/#navigate
> ...which, in step 4, just scrolls and aborts the algorithm without 
> actually changing the active Document object.

Hmm.  That algorithm doesn't look quite right in the case when going 
from http://example.com/#foo to http://example.com/.  That case should 
actually do the load instead of scrolling, last I checked, unless done 
as part of a history traversal.  See also 

Same thing for the case when going from http://example.com/ to 
http://example.com/ (as comment 5 in the above bug points out).  If I 
read the current draft right, per step 4 that would be a no-op, whereas 
in practice I don't believe it is in browsers...

Received on Wednesday, 8 July 2009 23:29:02 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:14 UTC