Closed Bug 2041144 Opened 3 months ago Closed 3 months ago

[wpt-sync] Sync PR 60018 - [Masonry] Add invalidation tests for grid-lanes properties

Categories

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

task

Tracking

()

RESOLVED FIXED
153 Branch
Tracking Status
firefox153 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Yanling Wang <yanlingwang@microsoft.com> wrote:

[Masonry] Add invalidation tests for grid-lanes properties

Several existing tests already cover dynamic change scenarios for
grid-lanes. This CL fills the remaining gaps by adding tests for
grid-lanes specific properties (grid-lanes-direction, grid-lanes-pack)
and adapting grid invalidation tests to verify grid-lanes behave
correctly for shared properties.

Bug: 343257585
Change-Id: Ibc1619e7c38c9a1e788ffd57e69229296aba9156
Reviewed-on: https://chromium-review.googlesource.com/7850522
WPT-Export-Revision: d0c2ed294b87bbb00e0b97d6d8af7a47f4a266e3

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

CI Results

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

Total 12 tests

Status Summary

Firefox

OK : 9
PASS: 2
FAIL: 41[Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt] 44[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt, GitHub]

Chrome

OK : 9
PASS: 46

Safari

OK : 9
PASS: 39
FAIL: 7

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

New Tests That Don't Pass

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