Closed Bug 1439633 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 9589 - [LayoutNG] Use containing block size correctly for abspos.

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla61
Tracking Flags:
Tracking Status
firefox61 --- fixed

People

(Reporter: mozilla.org, Unassigned)

Details

(Whiteboard: [wptsync downstream]) 

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

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

Morten Stenshorne wrote:
>  [LayoutNG] Use containing block size correctly for abspos.
>  
>  UpdateOutOfFlowBlockLayout() needs to deal with both the actual
>  containing block size, as specified by CSS (i.e. the padding box size),
>  and the border-box size of the object that is the containing block of an
>  absolutely positioned descendant.
>  
>  Some light cleanup. We always need the border sizes, so just calculate
>  them once, unconditionally. Also, there seems no need for a special path
>  for grid/flex, so I removed it.
>  
>  Some tests start to pass. They are still expected to fail in legacy.
>  
>  Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
>  Change-Id: I85462d76aa9fa3d0105bf079e59f7c2a7a70f117
>  
>  Reviewed-on: https://chromium-review.googlesource.com/926004
>  WPT-Export-Revision: 7553569b78e8d1d6b81a0aea12aabf32e0a1b073
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fb42cfd44ef8
[wpt PR 9589] - [LayoutNG] Use containing block size correctly for abspos., a=testonly
https://hg.mozilla.org/mozilla-central/rev/fb42cfd44ef8
Status: NEW → RESOLVED
Closed: 5 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.