Closed Bug 1463665 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 11115 - [css-grid] Content Alignment as part of the track sizing algorithm

Categories

(Core :: CSS Parsing and Computation, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 11115 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/11115 Details from upstream follow. Javier Fernandez <jfernandez@igalia.com> wrote: > [css-grid] Content Alignment as part of the track sizing algorithm > > The CSS WG resolved [1] that Content Alignment should account to the > track sizing algorithm. > > The sizing algorithm has been modified so that two new steps (1.5 > and 2.5) were added to compute the Content Alignment offsets after > resolving the columns' and rows' sizes respectively. > > Added WPT > * grid-content-distribution-must-account-for-track-sizing-001.html > * grid-content-distribution-must-account-for-track-sizing-002.html > > Bug: 844744 > Change-Id: I90019a96b148d3713467e35fde9482d0d39b1ced > > Reviewed-on: https://chromium-review.googlesource.com/1067918 > WPT-Export-Revision: b01f13fbd69a4b1be9a36f0283a9e20e6fa71e03
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 2 tests and 2 subtests OK : 2 PASS : 1 FAIL : 1 New tests that have failures or other problems: /css/css-grid/layout-algorithm/grid-content-distribution-must-account-for-track-sizing-002.html .grid 1: FAIL
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/96df24278a6c [wpt PR 11115] - [css-grid] Content Alignment as part of the track sizing algorithm, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/cbdb44a0731d [wpt PR 11115] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.