Closed
Bug 1441151
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 9673 - [LayoutNG] Need to lay out legacy objects to figure out their inline size.
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 9673 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/9673 Details from upstream follow. Morten Stenshorne wrote: > [LayoutNG] Need to lay out legacy objects to figure out their inline size. > > NG cannot always calculate the correct size of objects that are laid out > by the legacy engine, so just lay them out if we need to know their > size. > > The computed CSS width on a table may not end up as its used value, for > instance. > > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng > Change-Id: Iaa327ad21055d6c1af96241b5403193c8b4b5ba3 > Reviewed-on: https://chromium-review.googlesource.com/937261 > WPT-Export-Revision: d189e23686190389ff02b344007942d850818c9d
Reporter | ||
Updated•6 years ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Reporter | ||
Comment 1•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=1eac28f14ea6f91480e5a30a8d01b08ab130f9d9
Reporter | ||
Comment 2•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=060c7296c0850b2ba8728511fa2c4c498834ca77
Reporter | ||
Comment 3•6 years ago
|
||
Ran 1 tests PASS : 1
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/b1fc0811316c [wpt PR 9673] - [LayoutNG] Need to lay out legacy objects to figure out their inline size., a=testonly
Comment 5•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b1fc0811316c
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in
before you can comment on or make changes to this bug.
Description
•