Closed
Bug 1983546
Opened 7 months ago
Closed 7 months ago
Traverse navigate events are fired incorrectly.
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
FIXED
144 Branch
| Tracking | Status | |
|---|---|---|
| firefox144 | --- | fixed |
People
(Reporter: farre, Assigned: farre)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
There are two instance when the navigate events are fired incorrectly for traversals.
- when there are no event handlers on the navigation object but method trackers we skip firing the navigate event
- when we're performing a same document history traversal we still fire a push/replace/reload navigate event
| Assignee | ||
Updated•7 months ago
|
Assignee: nobody → afarre
Severity: -- → S3
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•7 months ago
|
||
In the same manner as with beforeunload we track when we need to fire a
traverse navigate event for the top level window context. This is
required when: any event handlers are registered on the window's
navigation object or when there are any ongoing or upcoming method
trackers associated with a window's navigation object.
Also make sure to not fire a push/replace/reload navigate event when
only a traverse navigate event should be fired.
Pushed by afarre@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/a9dce94db87a
https://hg.mozilla.org/integration/autoland/rev/df126e5491a1
Fire the navigate event correctly for history navigations. r=jjaschke
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
status-firefox144:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
Updated•6 months ago
|
QA Whiteboard: [qa-triage-done-c145/b144]
You need to log in
before you can comment on or make changes to this bug.
Description
•