Closed Bug 1721305 Opened 5 years ago Closed 4 years ago

[wpt-sync] Sync PR 29714 - AppHistoryNavigateEvent.navigationType, AppHistoryDestination.key, and AppHistoryDestination.id

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: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

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

AppHistoryNavigateEvent.navigationType, AppHistoryDestination.key, and AppHistoryDestination.id

navigationType is set to one of ("push", "replace", "reload", "traverse"), and
is derived from the WebFrameLoadType of the navigation.

key and id are set on AppHistoryDestination only in the "traverse" case,
because that is the only case where the key and id are known at the time
of the navigate event.

Bug: 1183545
Change-Id: I772418351931c3a74a45410001b51ea737da61a8
Reviewed-on: https://chromium-review.googlesource.com/3040051
WPT-Export-Revision: 0ec101844d3efa1d9c8aaba9cd99fc5fcf9eb9bb

CI Results

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

Total 23 tests and 1 subtests

Status Summary

Firefox

OK : 23
FAIL : 23

Chrome

OK : 19
PASS : 1
FAIL : 18
ERROR: 4

Safari

OK : 23
FAIL : 23

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/app-history/navigate-event/navigate-anchor-cross-origin.html
<a> cross-origin navigate event: FAIL (Safari: FAIL)
/app-history/navigate-event/navigate-anchor-fragment.html
Fragment <a> click fires navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-anchor-same-origin-cross-document.html
<a> cross-document (but same-origin) navigate event: FAIL (Safari: FAIL)
/app-history/navigate-event/navigate-anchor-userInitiated.html
Fragment <a> click fires navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-anchor-with-target.html
<a> with a target fires navigate event in target window but not source: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-appHistory-back-cross-document.html
navigate event for appHistory.back() - cross-document: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-appHistory-back-same-document.html
navigate event for appHistory.back() - same-document: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-appHistory-navigate.html
navigate event for appHistory.navigate(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-destination-getState-back-forward.html
navigate event destination.getState() on back/forward navigation: FAIL (Chrome: PASS, Safari: FAIL)
/app-history/navigate-event/navigate-destination-getState-navigate.html
navigate event destination.getState() should be the state given to navigate(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-form-userInitiated.html
<form> submission fires navigate event: FAIL (Safari: FAIL)
/app-history/navigate-event/navigate-form-with-target.html
<form> submission with a target fires navigate event in target window but not source: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-form.html
<form> submission fires navigate event: FAIL (Safari: FAIL)
/app-history/navigate-event/navigate-history-back-after-fragment.html
history.back() fires the navigate event and sets hashChange when reversing a fragment navigation: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-history-back-after-pushState.html
history.back() fires the navigate event when reversing a pushState(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-history-go-0.html
history.go(0) fires the navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-history-pushState.html
history.pushState() fires the navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-history-replaceState.html
history.replaceState() fires the navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-iframe-location.html
location API on another window fires navigate event in the target window only: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-location.html
location API fires navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-meta-refresh.html
<meta> refresh fires navigate event: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-window-open-self.html
window.open() fires navigate event when targeting self: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate-event/navigate-window-open.html
window.open() fires navigate event in target window but not source: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1db9d1463cd8 [wpt PR 29714] - AppHistoryNavigateEvent.navigationType, AppHistoryDestination.key, and AppHistoryDestination.id, a=testonly

https://hg.mozilla.org/mozilla-central/rev/1db9d1463cd8

Status: NEW → RESOLVED
Closed: 4 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.