Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CQ] Respect contain:style in ListItemOrdinal #37900

Merged
merged 1 commit into from Jan 13, 2023

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jan 12, 2023

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 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/c/chromium/src/+/4161712
Reviewed-by: Oriol Brufau <obrufau@igalia.com>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1092264}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

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 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/c/chromium/src/+/4161712
Reviewed-by: Oriol Brufau <obrufau@igalia.com>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1092264}
@jonathan-j-lee
Copy link
Contributor

Looks transient: #37918 (comment). Retrying.

@chromium-wpt-export-bot chromium-wpt-export-bot merged commit a7308e5 into master Jan 13, 2023
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-4161712 branch January 13, 2023 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants