Closed Bug 1986309 Opened 1 month ago Closed 1 month ago

#inner-navigate-event-firing-algorithm needs to wait on committed promise for failure steps as well

Categories

(Core :: DOM: Navigation, defect)

defect

Tracking

()

RESOLVED FIXED
144 Branch
Tracking Status
firefox144 --- fixed

People

(Reporter: farre, Assigned: farre)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

No description provided.
Assignee: nobody → afarre
Severity: -- → S3
Status: NEW → ASSIGNED

It turns out that we need this to guarantee event ordering with regard
to promises resolving and rejecting. This means that not only does the
success steps need to wait on method tracker committed promise, so does
the failure steps. But not only that, if we have handlers in the promise
list we need to really ensure that their promises are handled after a
committed promise.

Pushed by chorotan@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/08e663da3374 https://hg.mozilla.org/integration/autoland/rev/fe265da7b601 Revert "Bug 1986309 - Always wait on committed promise if there is an api method tracker. r=jjaschke" for causing build bustages at Navigation.cpp

Backed out for causing build bustages at Navigation.cpp

Backout link

Push with failures

Failure log

Flags: needinfo?(afarre)
Flags: needinfo?(afarre)
Regressions: 1986485
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
QA Whiteboard: [qa-triage-done-c145/b144]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: