mirror of
https://github.com/HeyPuter/firefox.git
synced 2026-11-13 20:14:57 -10:00
Morten Stenshorne
b667f0c17e
Automatic update from web-platform-tests Disable fragment traversal correctly when block frag is enabled. Once we've entered legacy multicol, nothing inside should do fragment traversal. The legacy multicol pre-paint code might create multiple FragmentData entries for monolithic forced LayoutNG objects (such as math and custom layout), because legacy layout doesn't really understand what monolithic means. This worked fine when LayoutNGBlockFragmentation was disabled, since we'd always disable fragmentation inside multicol then. But when the feature was enabled, we would allow fragment traversal of LayoutNG subtrees inside legacy multicol. Don't do that. The new test crashes with LayoutNG disabled (regardless of this fix), since the test uses the CSS layout API, which isn't supported when LayoutNG is disabled. Just skip it there. Bug: 1289999 Change-Id: Iacddb22eb3df224ea57f988f37409bd57b5f200d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3412124 Reviewed-by: Ian Kilpatrick <[email protected]> Commit-Queue: Morten Stenshorne <[email protected]> Cr-Commit-Position: refs/heads/main@{#963498} -- wpt-commits: 1d446b1678bc853f78c6f3a2f366be0574136928 wpt-pr: 32529
10 lines
434 B
HTML
10 lines
434 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=1289999">
|
|
<div style="columns:3; column-fill:auto; height:100px;">
|
|
<div style="display:flex;"></div>
|
|
<div style="display:grid;"></div>
|
|
<div style="display:table;"></div>
|
|
<div style="position:relative; display:layout(foo); height:150px;"></div>
|
|
</div>
|