[wpt-sync] Sync PR 29974 - App history: implement updateCurrent()
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox93 fixed)
| Tracking | Status | |
|---|---|---|
| firefox93 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 29974 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/29974
Details from upstream follow.
b'Domenic Denicola <domenic@chromium.org>' wrote:
App history: implement updateCurrent()
Follows https://github.com/WICG/app-history/pull/146.
Bug: 1183545
Change-Id: Iabf64f2363906a2c7f2ecbd4e7c4a0e48c0f1522
Reviewed-on: https://chromium-review.googlesource.com/3086123
WPT-Export-Revision: 0bb696ce29b78e1d1ceb3377c68d8733d808353e
| Assignee | ||
Comment 1•5 years ago
|
||
| Assignee | ||
Comment 2•5 years ago
|
||
CI Results
Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 14 tests and 2 subtests
Status Summary
Firefox
OK : 12
FAIL : 13
TIMEOUT: 2
ERROR : 2
Chrome
OK : 12
PASS : 2
FAIL : 11
TIMEOUT: 2
ERROR : 2
Safari
OK : 12
FAIL : 13
TIMEOUT: 2
ERROR : 2
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
/app-history/navigate/state/navigate-state-after-same-document-location-api-navigation.html: ERROR (Chrome: ERROR, Safari: ERROR)
appHistoryEntry.getState() behavior after navigating away and back via a fragment change: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/app-history/navigate/state/updateCurrent/basic.html
updateCurrent() works as expected: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/exception-order-initial-about-blank-unserializablestate.html
updateCurrent() with unserializable state on the initial about:blank must throw an "InvalidStateError", not a "DataCloneError": FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/exception-order-not-fully-active-unserializablestate.html
updateCurrent() with unserializable state while not fully active must throw an "InvalidStateError", not a "DataCloneError": FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/initial-about-blank.html
updateCurrent() must throw if the document is still on the initial about:blank: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/no-args.html
updateCurrent() must throw if state is not given: FAIL (Chrome: PASS, Safari: FAIL)
/app-history/navigate/state/updateCurrent/not-fully-active.html
updateCurrent() must throw if the document is not fully active: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/state-after-history-pushState.html
appHistoryEntry.getState() after history.pushState(): FAIL (Chrome: PASS, Safari: FAIL)
/app-history/navigate/state/updateCurrent/state-after-history-replaceState.html
appHistoryEntry.getState() after history.replaceState(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/state-after-reload.html
appHistoryEntry.getState() after location.reload(): FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/state-after-same-document-location-api-navigation.html: ERROR (Chrome: ERROR, Safari: ERROR)
appHistoryEntry.getState() behavior after navigating away and back via a fragment change: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/app-history/navigate/state/updateCurrent/state-cross-document-location-navigate.html
appHistoryEntry.getState() behavior after cross-document location API navigation: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/state-cross-document-restore.html
appHistoryEntry.getState() behavior after navigating away and back: FAIL (Chrome: FAIL, Safari: FAIL)
/app-history/navigate/state/updateCurrent/state-invalid.html
updateCurrent() must throw if state is unserializable (WritableStream): FAIL (Chrome: FAIL, Safari: FAIL)
updateCurrent() must throw if state is unserializable (SharedArrayBuffer): FAIL (Chrome: FAIL, Safari: FAIL)
Comment 4•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/252b414190ab
https://hg.mozilla.org/mozilla-central/rev/f3f71d950b2b
Description
•