Closed Bug 1809865 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 37900 - [CQ] Respect contain:style in ListItemOrdinal

Categories

(Core :: Layout, task, P4)

Product:
Core
Component:
Layout
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
111 Branch
Tracking Flags:
Tracking Status
firefox111 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Anders Hartvoll Ruud <andruud@chromium.org> wrote:

[CQ] Respect contain:style in ListItemOrdinal

In e.g. a reversed list with automatic ordinals, the style recalc of
an element may cause invalidation of "previous" LayoutObjects.
If this happens during interleaved style recalc, then we may dirty
LayoutObjects that we're already done laying out.

This CL addresses this by considering style containment in during
ordinal calculations in ListItemOrdinal. Instead of always considering
the enclosing list as the scope for the current counter, we now also
treat intermediate elements with contain:style as such.

Fixed: 1377644
Change-Id: I7d4d9e7fd84e061a28ae40f3bae280b9d55558a0
Reviewed-on: https://chromium-review.googlesource.com/4161712
WPT-Export-Revision: aa7a6934a10642cbaf2239f4ca5307e7bf2bfc31

Component: web-platform-tests → Layout
Product: Testing → Core
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/058d3fc39536 [wpt PR 37900] - [CQ] Respect contain:style in ListItemOrdinal, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/058d3fc39536

Status: REOPENED → RESOLVED
Closed: 2 years ago → 2 years ago
status-firefox111: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.