mirror of
https://github.com/HeyPuter/firefox.git
synced 2026-11-13 20:14:57 -10:00
Morten Stenshorne
b5a7b6a963
Automatic update from web-platform-tests
Properly disallow custom layout + multicol.
Checking LayoutObject type won't do, since we don't always create a
LayoutNGCustom object (e.g. if it's a DETAILS element (but, then again,
should we allow custom layout on those???)). Check display type instead.
The reason for the crash was that we ended up creating a
LayoutNGBlockFragmentation multicol container inside a legacy multicol
container, even when LayoutNGBlockFragmentation is disabled (custom
layout forces LayoutNG). We don't create a paint layer on the flow
thread (nor the multicol container) in LayoutNGBlockFragmentation, which
the legacy pre-paint code assumes.
Bug: 1219874
Change-Id: I26fcd8d4a5fd51ce1799b207bf39b8e322890ca9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2964675
Reviewed-by: Xianzhu Wang <[email protected]>
Reviewed-by: Ian Kilpatrick <[email protected]>
Commit-Queue: Morten Stenshorne <[email protected]>
Cr-Commit-Position: refs/heads/master@{#893340}
--
wpt-commits: 944917215322834033024fa37ce58eb13c2fa3ee
wpt-pr: 29403
7 lines
279 B
HTML
7 lines
279 B
HTML
<!DOCTYPE html>
|
|
<link rel="author" title="Morten Stenshorne" href="mailto:[email protected]">
|
|
<link rel="help" href="https://bugs.chromium.org/p/chromium/issues/detail?id=1219874">
|
|
<div style="columns:2;">
|
|
<details style="display:layout(foo); columns:2;"></details>
|
|
</div>
|