Closed
Bug 1850187
Opened 1 year ago
Closed 1 year ago
[wpt-sync] Sync PR 41649 - [GridNG] Fix grid shorthand parsing
Categories
(Core :: Layout: Grid, task, P4)
Core
Layout: Grid
Tracking
()
RESOLVED
FIXED
119 Branch
Tracking | Status | |
---|---|---|
firefox119 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 41649 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/41649
Details from upstream follow.
Kurt Catti-Schmidt <kschmi@microsoft.com> wrote:
[GridNG] Fix grid shorthand parsing
This change updates grid shorthand parsing to be compliant with the
spec. There were several subtle edge cases that were not being accounted
for. This includes differentiating between specified and implicit
initial values, and a few cases where we were incorrectly returning
early.Bug: 1370841
Change-Id: If33f250f1e07ea36a159c84928202daf0f328d7b
Reviewed-on: https://chromium-review.googlesource.com/4815008
WPT-Export-Revision: db60e927560bc8ce394c0d67f03cf865a9aced59
Assignee | ||
Updated•1 year ago
|
Component: web-platform-tests → Layout: Grid
Product: Testing → Core
Assignee | ||
Comment 1•1 year ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=5d42f7d777f7c0b0358f932389efc89ee1e93280
Assignee | ||
Comment 2•1 year ago
|
||
Test result changes from PR not available.
Assignee | ||
Comment 3•1 year ago
|
||
Test result changes from PR not available.
Assignee | ||
Comment 4•1 year ago
|
||
Test result changes from PR not available.
Assignee | ||
Comment 5•1 year ago
|
||
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2289c378c6d1
[wpt PR 41649] - [GridNG] Fix grid shorthand parsing, a=testonly
Comment 7•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox119:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•