Open Bug 1183881 Opened 9 years ago Updated 2 years ago

history.state is reset to null without dispatching popstate after "navigating" to the same hash

Categories

(Core :: DOM: Navigation, defect)

39 Branch
defect

Tracking

()

People

(Reporter: robwu, Assigned: smaug)

Details

Attachments

(1 file)

1. Open the test file (this will automatically replace the history entry with #atarget and some value in history.state).
2. Click on the link (to the identical #atarget).

Expected result:
Either of the following:
- The history state should not change, since the link target is identical.
- history.state becomes null, but the popstate event is fired so that the application is aware of this change.

Actual result:
- history.state is set to null, without any notifications.
Flags: needinfo?(bugs)
This problem happens within two scenarios:

- A button/link with current url is clicked
- The webpage is refreshed by enter trough navBar.

With this bug I can't track the state that has been pushed therefore it will duplicate it un the history.
Assignee: nobody → bugs
Flags: needinfo?(bugs)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: