Closed Bug 1518355 Opened 8 months ago Closed 7 months ago

[wpt-sync] Sync PR 14742 - [LayoutNG] Legacy split inline abspos crash fix

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Aleks Totic <atotic@chromium.org> wrote:

[LayoutNG] Legacy split inline abspos crash fix

We cannot perform special-case inline split multiple
anonymous block OOF container processing when
OOF Element is positioned by Legacy.

Legacy expects OOF positioned Element to always be positioned by its
Container().

I've also updated the comments to better describe this tricky code.

Bug: 919415
Change-Id: I77ed335bbce4bf63c78e7046835ff7ff1264b3cc
Reviewed-on: https://chromium-review.googlesource.com/1399541
WPT-Export-Revision: 2075db98d7806eb490f21f8d476871e79af01e62

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 1 tests and 1 subtests
OK     : 1
PASS   : 1
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e737639fc29c
[wpt PR 14742] - [LayoutNG] Legacy split inline abspos crash fix, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e8f112481da0
[wpt PR 14742] - [LayoutNG] Legacy split inline abspos crash fix, a=testonly
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.