Closed Bug 1583118 Opened 2 years ago Closed 1 year ago

[wpt-sync] Sync PR 19216 - AOM Phase 4: Element Reflection tests for scoping.

Categories

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

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Meredith Lane <meredithl@chromium.org> wrote:

AOM Phase 4: Element Reflection tests for scoping.

Adds in extra test cases relating to moving elements in and out of scope.
This behaviour is still under discussion, so is likely to change in future
as the API is finalized.

Also fixes up some minor editorial tweaks that were missed in the previous CL.

Bug=981423

Change-Id: I5863b1f8d7ab1b6287af1d95e859945af38fea60
Reviewed-on: https://chromium-review.googlesource.com/1816496
WPT-Export-Revision: 0fe4ff7f25f65d05e9b684d9015e2798341a03bb

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

GitHub CI Results

wpt.fyi PR Results Base Results

Ran 1 tests and 17 subtests

Firefox

OK : 1
FAIL: 17

Chrome

OK : 1
PASS: 16
FAIL: 1

Safari

OK : 1
FAIL: 17

New tests that's don't pass

/dom/nodes/aria-element-reflection.tentative.html
Moving explicitly set elements around within the same scope, and removing from the DOM.: Firefox: FAIL, Chrome: FAIL, Safari: FAIL
Moving explicitly set elements across shadow DOM boundaries.: Firefox: FAIL, Chrome: PASS, Safari: FAIL

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4e1ae53e712c
[wpt PR 19216] - [AOM] Element Reflection tests for scoping., a=testonly
https://hg.mozilla.org/integration/autoland/rev/59882c4a2e11
[wpt PR 19216] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.