24303 2014-01-15 23:39:20 +0000 location.reload() when document address has a fragment should not cause just fragment navigation 2014-01-16 17:51:28 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED FIXED P2 normal Unsorted 24302 1 silviapfeiffer1 ian ian kornstaedt mike public-html-admin public-html-wg-issue-tracking contributor oldest_to_newest 98541 0 silviapfeiffer1 2014-01-15 23:39:20 +0000 +++ 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. 98640 1 ian 2014-01-16 17:51:20 +0000 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 98641 2 contributor 2014-01-16 17:51:28 +0000 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