Closed Bug 1794848 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 36414 - Fix various issues with the new non-fully-active.html test

Categories

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

task

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox108 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Chris Dumez <cdumez@apple.com> wrote:

Fix various issues with the new non-fully-active.html test

The test was missing a body so the instruction to append an iframe to the body would fail. The various exception check would also fail because their were not using the right global.

PR 36414 applied with additional changes from upstream: 7535da1a428e04393fc23d0b3c5ddc38fd3904cc
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 1 tests and 3 subtests

Status Summary

Firefox

OK : 1
FAIL : 3

Chrome

PASS : 1
FAIL : 1
TIMEOUT: 2

Safari

OK : 1
FAIL : 3

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /screen-orientation/non-fully-active.html [wpt.fyi]
    • Attempting to lock non-fully active documents results in a InvalidStateError: FAIL (Chrome: PASS, Safari: FAIL)
    • Attempting to unlock non-fully active documents results in a InvalidStateError: FAIL (Chrome: FAIL, Safari: FAIL)
    • Making a document non-fully active while locking results in an AbortError: FAIL (Chrome: TIMEOUT, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/811dbe461d87 [wpt PR 36414] - Fix various issues with the new non-fully-active.html test, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.