Closed Bug 1750720 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 32431 - Avoid incorrect legacy layout fallback inside NG-only display types.

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
98 Branch
Tracking Status
firefox98 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

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/3398110
WPT-Export-Revision: 37bbcf4cf054d2e7256ab8eaf0bb690397c9e850

Component: web-platform-tests → Layout
Product: Testing → Core

CI Results

Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 3 tests

Status Summary

Firefox

PASS : 3

Chrome

CRASH: 3

Safari

PASS : 3

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
You need to log in before you can comment on or make changes to this bug.