Closed Bug 1526388 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 15160 - [LayoutNG] Provide both inline resolution sizes to legacy.

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

[LayoutNG] Provide both inline resolution sizes to legacy.

When entering legacy layout from NG, we need to provide both percentage
resolution inline size and available inline size.

Available size is used when using the fill-available measure, i.e. what
typically takes place when inline-size is auto. Percentage resolution
size is used otherwise (to resolve percentages). We used to provide
percentage size if inline-size was percentage based, and available size
otherwise. But there are cases where we need both. Any of inline-size,
inline-min-size and inline-max-size may or may not be percentage based,
and letting the unit type of inline-size decide therefore won't do.

Change-Id: I225372584a88471dad35deddbc2d3a7de732583a
Reviewed-on: https://chromium-review.googlesource.com/c/1443992
Reviewed-by: Christian Biesinger \<cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick \<ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne \<mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627885}

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 3 tests and 3 subtests
OK     : 3
PASS   : 3
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/67afc9066879
[wpt PR 15160] - [LayoutNG] Provide both inline resolution sizes to legacy., a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.