Closed Bug 1687719 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 27256 - Update `SlotAssignmentMode` to `name` from `auto` to match the latest proposal

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
87 Branch
Tracking Flags:
Tracking Status
firefox87 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

b'Tetsuharu Ohzeki <tetsuharu.ohzeki@gmail.com>' wrote:

Update SlotAssignmentMode to name from auto to match the latest proposal

By the latest proposal, SlotAssignmentMode value is changed to name from auto.

This change follows it.

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

CI Results

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

Total 1 tests and 16 subtests

Status Summary

Firefox

OK : 1
FAIL: 16

Chrome

OK : 1
PASS: 15
FAIL: 1

Safari

OK : 1
FAIL: 16

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/shadow-dom/slots-imperative-slot-api.tentative.html
attachShadow can take slotAssignment parameter.: FAIL (Chrome: FAIL, Safari: FAIL)
Imperative slot API throws exception when not slotAssignment != 'manual'.: FAIL (Chrome: PASS, Safari: FAIL)
Imperative slot API throws exception when slottable parentNode != slot's host.: FAIL (Chrome: PASS, Safari: FAIL)
Imperative slot API can assign nodes in manual slot assignment.: FAIL (Chrome: PASS, Safari: FAIL)
Order of slottables is preserved in manual slot assignment.: FAIL (Chrome: PASS, Safari: FAIL)
Previously assigned slottable is moved to new slot when it's reassigned.: FAIL (Chrome: PASS, Safari: FAIL)
Order and assignment of nodes are preserved during multiple assignment in a row.: FAIL (Chrome: PASS, Safari: FAIL)
Assigning invalid nodes causes exception and slot returns to its previous state.: FAIL (Chrome: PASS, Safari: FAIL)
Moving a slot to a new host, the slot loses its previously assigned slottables.: FAIL (Chrome: PASS, Safari: FAIL)
Moving a slot's tree order position within a shadow host has no impact on its assigned slottables.: FAIL (Chrome: PASS, Safari: FAIL)
Appending slottable to different host, it loses slot assignment. It can be re-assigned within a new host.: FAIL (Chrome: PASS, Safari: FAIL)
Previously assigned node should not be assigned if slot moved to a new shadow root. The slot remains empty when moved back, no trigger recalc.: FAIL (Chrome: PASS, Safari: FAIL)
Previously assigned node should not be assigned if slot moved to a new shadow root. The slot remains empty when moved back, trigger recalc.: FAIL (Chrome: PASS, Safari: FAIL)
Assignment with the same node in parameters should be ignored, last one wins.: FAIL (Chrome: PASS, Safari: FAIL)
Removing a slot from DOM resets its slottable's slot assignment.: FAIL (Chrome: PASS, Safari: FAIL)
A slot should be cleared of assigned nodes even if it's re-inserted into the same shadow root.: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/84ac1dad8457
[wpt PR 27256] - Update `SlotAssignmentMode` to `name` from `auto` to match the latest proposal, a=testonly

https://hg.mozilla.org/mozilla-central/rev/84ac1dad8457

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox87: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch
You need to log in before you can comment on or make changes to this bug.