Closed Bug 1461461 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 10994 - [LayoutNG] Fix min/max sizes during layout and intrinsic passes.

Categories

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

Product:
Core
Component:
CSS Parsing and Computation
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla62
Tracking Flags:
Tracking Status
firefox62 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

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

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

Ian Kilpatrick <ikilpatrick@chromium.org> wrote:
>  [LayoutNG] Fix min/max sizes during layout and intrinsic passes.
>  
>  Essentially this boils down to during min/max auto/percent/calc should be
>  treated the same, either being border+padding or infinity.
>  
>  And during layout they should be taken into account.
>  
>  I added some tests which now match FF/Edge (004,005) which LayoutNG matches, but
>  existing layout fails. The primary difference is change by passing kContent into
>  ResolveBlockLength during the ComputeBlockSizeForFragment function.
>  
>  Bug: 635619
>  Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
>  Change-Id: I4e0c171a0e29ea5d85a742d85df001647813c1f3
>  
>  Reviewed-on: https://chromium-review.googlesource.com/1056291
>  WPT-Export-Revision: d9bad9421781eab3763a3b973b57666fb3a61dcc
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 2 tests
PASS   : 2
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6d59c2e00ab1
[wpt PR 10994] - [LayoutNG] Fix min/max sizes during layout and intrinsic passes., a=testonly
https://hg.mozilla.org/mozilla-central/rev/6d59c2e00ab1
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox62: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.