Closed Bug 1944250 Opened 16 days ago Closed 14 days ago

[wpt-sync] Sync PR 50332 - Skip interactivity:inert for window.find()

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
136 Branch
Tracking Status
firefox136 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

Skip interactivity:inert for window.find()

Inert elements may have non-inert descendants when made inert by the
interactivity property. Stop trying doing anything smart for modal and
fullscreen elements.

TEST=external/wpt/inert/inert-with-fullscreen-element.html
TEST=external/wpt/inert/inert-with-modal-dialog-003.html

Bug: 370065759
Change-Id: I48396644a9cf58ca6fc949ee66f9c1e7d34131fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6198191
Auto-Submit: Rune Lillesveen \<futhark@chromium.org>
Commit-Queue: Steinar H Gunderson \<sesse@chromium.org>
Reviewed-by: Steinar H Gunderson \<sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1412177}

Component: web-platform-tests → Layout
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
PASS: 2
FAIL: 1

Chrome

OK : 1
PASS: 2
FAIL: 1

Safari

OK : 1
PASS: 2
FAIL: 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/eb63ab065964 [wpt PR 50332] - Skip interactivity:inert for window.find(), a=testonly https://hg.mozilla.org/integration/autoland/rev/d07ff3e932a4 [wpt PR 50332] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 14 days ago
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
You need to log in before you can comment on or make changes to this bug.