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 24302 - 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: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 24303
  Show dependency treegraph
 
Reported: 2014-01-15 20:49 UTC by Leif Kornstaedt
Modified: 2014-02-16 02:40 UTC (History)
4 users (show)

See Also:


Attachments

Description Leif Kornstaedt 2014-01-15 20:49:14 UTC
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 Silvia Pfeiffer 2014-02-16 02:40:40 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted

Change Description:
https://github.com/w3c/html/commit/9c908403b0654318c3b2371f8ca14076f41bc8d4

Rationale: change accepted as provided by WHATWG