This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24303 - location.reload() when document address has a fragment should not cause just fragment navigation
Summary: location.reload() when document address has a fragment should not cause just ...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on: 24302
Blocks:
  Show dependency tree / graph
 
Reported: 2014-01-15 23:39 UTC by Silvia Pfeiffer
Modified: 2014-01-16 17:51 UTC (History)
5 users (show)

See Also:

Attachments

Description Silvia Pfeiffer 2014-01-15 23:39:20 UTC 
+++ This bug was initially created as a clone of Bug #24302 +++

location.reload() is specified to cause a regular navigation, and nothing in the initial six steps of the navigation algorithm seems to specifically prevent reload() from reaching the step labeled "Fragment identifiers".  So reload() could end up causing just a fragment navigation.

This doesn't correspond to the behavior of real browsers, where reload() always causes a re-fetch of the document, even if the document address has a fragment.
Comment 1 Ian 'Hixie' Hickson 2014-01-16 17:51:20 UTC 
Leif: Thanks for this bug. I have updated the WHATWG HTML standard accordingly. In future, if you wish to file bugs on the HTML standard, I recommend using the widget at the bottom right of the specification (http://whatwg.org/html), or filing a bug using this bug report link: http://whatwg.org/newbug
Comment 2 contributor 2014-01-16 17:51:28 UTC 
Checked in as WHATWG revision r8400.
Check-in comment: Turns out location.reload() does work even when you have a fragment identifier...
http://html5.org/tools/web-apps-tracker?from=8399&to=8400