Closed Bug 2022158 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 58380 - Only reset ongoing navigate event when it was the original one

Categories

(Core :: DOM: Navigation, task, P4)

Product:
Core
Component:
DOM: Navigation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
150 Branch
Tracking Flags:
Tracking Status
firefox150 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 58380 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/58380
Details from upstream follow.

Noam Rosenthal <nrosenthal@chromium.org> wrote:

Only reset ongoing navigate event when it was the original one

This protects from the scenario where an abort signal re-navigates.

Bug: 488475824
Change-Id: Ia278c28987227efa9aeff19a62fc5128ff9f8ed6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7649269
Reviewed-by: Nate Chapin \<japhet@chromium.org>
Commit-Queue: Noam Rosenthal \<nrosenthal@google.com>
Cr-Commit-Position: refs/heads/main@{#1596677}

Component: web-platform-tests → DOM: Navigation
Product: Testing → Core
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/b8c0c4248392 https://hg.mozilla.org/integration/autoland/rev/632fc695fcd2 [wpt PR 58380] - Only reset ongoing navigate event when it was the original one, a=testonly

https://hg.mozilla.org/mozilla-central/rev/632fc695fcd2

Status: NEW → RESOLVED
Closed: 2 months ago
status-firefox150: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 150 Branch
You need to log in before you can comment on or make changes to this bug.