Closed Bug 1882221 Opened 9 months ago Closed 9 months ago

[wpt-sync] Sync PR 44804 - [bfcache]Report navigation-failure

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
125 Branch
Tracking Status
firefox125 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

rubberyuzu <yuzus@chromium.org> wrote:

[bfcache]Report navigation-failure

This CL makes NotRestoredReasons API report navigation-failure for the
cases when HTTP status is not okay. This is to conform to the specced
reason name.

Change-Id: Ia06b5e704a1dfab8efb51b2b8a1d922edb5abfc9
Reviewed-on: https://chromium-review.googlesource.com/5326536
WPT-Export-Revision: e46459551e26991d58f158bfd7c060c7adadd7db

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 32 tests and 1 subtests

Status Summary

Firefox

OK : 28
PASS : 8
FAIL : 15
PRECONDITION_FAILED: 7
TIMEOUT : 2
ERROR : 3

Chrome

OK : 30
PASS : 30
FAIL : 4
PRECONDITION_FAILED: 7
TIMEOUT : 5

Safari

OK : 26
PASS : 3
FAIL : 20
PRECONDITION_FAILED: 4
TIMEOUT : 6
ERROR : 3
NOTRUN : 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4c011e2afdd5 [wpt PR 44804] - [bfcache]Report navigation-failure instead of http-status-not-ok, a=testonly
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch
You need to log in before you can comment on or make changes to this bug.