Closed Bug 1846285 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41246 - Enforce <details name> exclusivity in disconnected subtrees.

Categories

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

task

Tracking

()

RESOLVED FIXED
118 Branch
Tracking Status
firefox118 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

L. David Baron <dbaron@chromium.org> wrote:

Enforce <details name> exclusivity in disconnected subtrees.

See discussions in:
https://github.com/whatwg/html/pull/9400#discussion_r1231851118
https://github.com/openui/open-ui/issues/778#issuecomment-1634732524

Bug: 1444057
Change-Id: I901e4e3958cdf55a07cb9e5126ed235a07819228
Reviewed-on: https://chromium-review.googlesource.com/4734191
WPT-Export-Revision: 1a224ce31813683b52de93be9f4a47f469d4791e

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

CI Results

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

Total 1 tests and 14 subtests

Status Summary

Firefox

OK : 1
PASS: 1
FAIL: 13

Chrome

OK : 1
PASS: 11
FAIL: 3

Safari

OK : 1
PASS: 1
FAIL: 13

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /html/semantics/interactive-elements/the-details-element/name-attribute.tentative.html [wpt.fyi]
    • basic handling of mutually exclusive details: FAIL (Chrome: PASS, Safari: FAIL)
    • more complex handling of mutually exclusive details: FAIL (Chrome: PASS, Safari: FAIL)
    • mutually exclusive details across multiple names and multiple tree scopes: FAIL (Chrome: PASS, Safari: FAIL)
    • mutation event and toggle event order matches tree order: FAIL (Chrome: PASS, Safari: FAIL)
    • interaction of open attribute changes with mutation events: FAIL (Chrome: PASS, Safari: FAIL)
    • exclusivity enforcement with attachment scenario connected: FAIL (Chrome: PASS, Safari: FAIL)
    • exclusivity enforcement with attachment scenario disconnected: FAIL (Chrome: FAIL, Safari: FAIL)
    • exclusivity enforcement with attachment scenario shadow: FAIL (Chrome: PASS, Safari: FAIL)
    • exclusivity enforcement with attachment scenario shadow-in-disconnected: FAIL (Chrome: PASS, Safari: FAIL)
    • exclusivity enforcement with attachment scenario template-in-disconnected: FAIL (Chrome: FAIL, Safari: FAIL)
    • exclusivity enforcement with attachment scenario connected-in-xhr-response: FAIL (Chrome: PASS, Safari: FAIL)
    • exclusivity enforcement with attachment scenario connected-in-implementation-create-document: FAIL (Chrome: PASS, Safari: FAIL)
    • exclusivity enforcement with attachment scenario connected-in-template: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by ctuns@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/832f4e4adfc9 [wpt PR 41246] - Enforce <details name> exclusivity in disconnected subtrees., a=testonly https://hg.mozilla.org/mozilla-central/rev/c26e1d2ce592 [wpt PR 41246] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in before you can comment on or make changes to this bug.