forked from mirrors/gecko-dev
fca7a88236
Automatic update from web-platform-tests Avoid incorrect legacy layout fallback inside NG-only display types. NG-only display types (such as math and custom layout) will be treated as monolithic if they occur inside a legacy multicol container, so we don't have to let the ancestry trigger legacy layout fallback inside. Besides, it would be bad, as we'd end up mixing NG and legacy objects where this isn't allowed. It's only allowed at formatting context boundaries, and not e.g. between a table section and a table row. Bug: 1287843 Change-Id: I964a36ed2c4f94b06c35347475898971376d8670 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3398110 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#960361} -- wpt-commits: fdd4225082eee434df5293599b398bf5ae1189df wpt-pr: 32431
18 lines
567 B
HTML
18 lines
567 B
HTML
<!DOCTYPE html>
|
|
<link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
|
|
<link rel="help" href="https://bugs.chromium.org/p/chromium/issues/detail?id=1287843">
|
|
<div style="columns:2;">
|
|
<div style="display:layout(foo);">
|
|
<div>
|
|
<div style="display:inline-table;">
|
|
<div style="display:table-row;">
|
|
<div style="columns:2;">
|
|
<div style="display:inline-table;">
|
|
<div style="display:table-row;"></div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|