Closed Bug 2050698 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 60914 - [Masonry] Don't inherit line names into auto-placed subgrids

Categories

(Core :: Layout: Grid, task, P4)

task

Tracking

()

RESOLVED FIXED
154 Branch
Tracking Status
firefox154 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Alison Maher <almaher@microsoft.com> wrote:

[Masonry] Don't inherit line names into auto-placed subgrids

Per CSS Grid Level 3 [1], a subgrid that is auto-placed within a grid
lanes container must not inherit line names or named areas from that
container: its position in the grid axis is unknown at line-name
resolution time, so there is no valid mapping from the container's lines
to the subgrid's.

This applies only between an auto-placed subgrid and its direct grid
lanes parent. Nested subgrids still inherit line names from their own
subgrid parent, but none inherit the grid lanes container's lines.

[1] https://drafts.csswg.org/css-grid-3/#subgrids

Bug: 343257585
Change-Id: Ic19e18d1b743a9c35f1afa7a0faddd3783ef3fc7
Reviewed-on: https://chromium-review.googlesource.com/7997264
WPT-Export-Revision: 3054067ee2f6bcfc3e6038ae8d095da6372ea8e4

PR 60914 applied with additional changes from upstream: 25a20192274205f33cf7910dc7b925dd83f6c51d

Component: web-platform-tests → Layout: Grid
Product: Testing → Core

CI Results

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

Total 6 tests

Status Summary

Firefox

PASS: 1
FAIL: 5

Chrome

PASS: 2
FAIL: 4

Safari

PASS: 5
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

New Tests That Don't Pass

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch
You need to log in before you can comment on or make changes to this bug.