[Bug 24303] New: location.reload() when document address has a fragment should not cause just fragment navigation

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24303

            Bug ID: 24303
           Summary: location.reload() when document address has a fragment
                    should not cause just fragment navigation
           Product: WHATWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML
          Assignee: ian@hixie.ch
          Reporter: silviapfeiffer1@gmail.com
        QA Contact: contributor@whatwg.org
                CC: kornstaedt@hotmail.com, mike@w3.org,
                    public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org
        Depends on: 24302

+++ 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 15 January 2014 23:39:21 UTC