Closed Bug 1733160 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 30951 - Implement AppHistoryCurrentChangeEvent

Categories

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

task

Tracking

(firefox95 fixed)

RESOLVED FIXED
95 Branch
Tracking Status
firefox95 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Nate Chapin <japhet@chromium.org> wrote:

Implement AppHistoryCurrentChangeEvent

Spec/explainer: https://github.com/WICG/app-history/pull/171

Bug: 1252532
Change-Id: Ibd8a856fc36b37d5f4095627808a9a0be15de283
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3182849
Reviewed-by: Domenic Denicola \<domenic@chromium.org>
Commit-Queue: Nate Chapin \<japhet@chromium.org>
Cr-Commit-Position: refs/heads/main@{#924964}

CI Results

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

Total 22 tests and 4 subtests

Status Summary

Firefox

OK : 22
FAIL : 25

Chrome

OK : 20
PASS : 7
FAIL : 17
TIMEOUT: 2
ERROR : 1

Safari

OK : 22
FAIL : 25

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/app-history/currentchange-event/currentchange-anchor-href.html
AppHistoryCurrentChangeEvent fires for link click: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-back-forward-cross-doc.html
AppHistoryCurrentChangeEvent does not fire for cross-document appHistory.back() and appHistory.forward(): FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-back-forward-same-doc.html
AppHistoryCurrentChangeEvent fires for appHistory.back() and appHistory.forward(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-cross-doc.html
AppHistoryCurrentChangeEvent does not fire for cross-document appHistory.navigate(): FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-preventDefault.html
AppHistoryCurrentChangeEvent does not fire when onnavigate preventDefault() is called: FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-replace-cross-doc.html
AppHistoryCurrentChangeEvent does not fire for cross-document appHistory.navigate() with replace: FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-replace-same-doc.html
AppHistoryCurrentChangeEvent fires for appHistory.navigate() with replace: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-replace-transitionWhile.html
AppHistoryCurrentChangeEvent fires for appHistory.navigate() with replace intercepted by transitionWhile: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-same-doc.html
AppHistoryCurrentChangeEvent fires for appHistory.navigate(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-navigate-transitionWhile.html
AppHistoryCurrentChangeEvent fires for appHistory.navigate() intercepted by transitionWhile: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-reload-cross-doc.html
AppHistoryCurrentChangeEvent does not fire for cross-document appHistory.reload(): FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-reload-transitionWhile.html
AppHistoryCurrentChangeEvent fires for appHistory.reload() intercepted by transitionWhile: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-app-history-updateCurrent.html
AppHistoryCurrentChangeEvent fires for appHistory.updateCurrent(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-dispose-ordering.html
Ordering between AppHistoryCurrentChangeEvent and AppHistoryEntry dispose events: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-history-back-same-doc.html
AppHistoryCurrentChangeEvent fires for history.back(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-history-pushState.html
AppHistoryCurrentChangeEvent fires for history.pushState(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-history-replaceState.html
AppHistoryCurrentChangeEvent fires for history.replaceState(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-location-api.html
AppHistoryCurrentChangeEvent fires for location API navigations: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/currentchange-event/currentchange-navigate-from-initial-about-blank-same-doc.html
AppHistoryCurrentChangeEvent does not fire when navigating away from the initial about:blank: FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-navigate-from-initial-about-blank.html
AppHistoryCurrentChangeEvent does not fire when navigating away from the initial about:blank: FAIL (Chrome: PASS, Safari: FAIL)
/app-history/currentchange-event/currentchange-properties.html
AppHistoryCurrentChangeEvent's properties: FAIL (Chrome: TIMEOUT, Safari: FAIL)
/app-history/currentchange-event/event-constructor.html
can't bypass required members by omitting the dictionary entirely: FAIL (Chrome: FAIL, Safari: FAIL)
from is required: FAIL (Chrome: FAIL, Safari: FAIL)
all properties are reflected back: FAIL (Chrome: FAIL, Safari: FAIL)
defaults are as expected: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7a6adac4d296 [wpt PR 30951] - Implement AppHistoryCurrentChangeEvent, a=testonly https://hg.mozilla.org/integration/autoland/rev/378fdc3ef654 [wpt PR 30951] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
You need to log in before you can comment on or make changes to this bug.