Closed Bug 1720587 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 29668 - Implement AppHistoryNavigateEvent.signal

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox92 fixed)

Status:
RESOLVED FIXED
Milestone:
92 Branch
Tracking Flags:
Tracking Status
firefox92 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

b'Nate Chapin <japhet@chromium.org>' wrote:

Implement AppHistoryNavigateEvent.signal

This AbortSignal is associated with the ongoing navigation, and will
be signaled if the navigation is aborted, allowing dependent work
to listen for navigate abort.

Bug: 1183545
Change-Id: Iee841079fcc618bdb16c33875c1ac81cdc572ae7

Reviewed-on: https://chromium-review.googlesource.com/2877951
WPT-Export-Revision: 143403f22dc4e3a9e2dc1c508727eb54a5e91165

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 6 tests and 1 subtests

Status Summary

Firefox

OK : 6
FAIL : 6

Chrome

OK : 3
FAIL : 3
ERROR: 3

Safari

OK : 6
FAIL : 6

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/app-history/navigate-event/signal-abort-detach-in-onnavigate.html
window detach inside AppHistoryNavigateEvent signals AppHistoryNavigateEvent.signal: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/signal-abort-preventDefault.html
AppHistoryNavigateEvent.preventDefault signals AppHistoryNavigateEvent.signal: FAIL (Safari: FAIL)
/app-history/navigate-event/signal-abort-respondWith.html
AppHistoryNavigateEvent.respondWith does not signal AppHistoryNavigateEvent.signal: FAIL (Safari: FAIL)
/app-history/navigate-event/signal-abort-window-stop-after-respondWith.html
window.stop() cancels AppHistoryNavigateEvent.respondWith and signals AppHistoryNavigateEvent.signal: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/signal-abort-window-stop-in-onnavigate.html
window.stop() signals AppHistoryNavigateEvent.signal inside a navigate event handler: FAIL (Safari: FAIL)
/app-history/navigate-event/signal-abort-window-stop.html
window.stop() signals AppHistoryNavigateEvent.signal: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/23cf1f2136db
[wpt PR 29668] - Implement AppHistoryNavigateEvent.signal, a=testonly
https://hg.mozilla.org/integration/autoland/rev/6fd5af5cf973
[wpt PR 29668] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/23cf1f2136db
https://hg.mozilla.org/mozilla-central/rev/6fd5af5cf973

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox92: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
You need to log in before you can comment on or make changes to this bug.