Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[scroll-marker] Adhere more closely to active marker selection algo #52305

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

Merged
merged 1 commit into from
May 2, 2025

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

In the linked bug, we select a scroll marker while its target element
is not even within the scrollport.

This patch addresses this by adhering more closely to the spec'd
algorithm[1] which addresses this situation by stipulating that a
scroll target whose scroll position has not yet been reached should
only be selected if it is within half a scroll port of the current
scroll position.

We have clarified that although the algorithm[1] is not presented as
normative at the moment, the intention is to make it normative at some
point in the future.

[1] https://drafts.csswg.org/css-overflow-5/#example-d2ca6884

Bug: 413645441
Change-Id: I620cfa8a06cbd4f8f904fdaaef250351110b56dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6505661
Commit-Queue: David Awogbemila <[email protected]>
Reviewed-by: Steve Kobes <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1455009}

In the linked bug, we select a scroll marker while its target element
is not even within the scrollport.

This patch addresses this by adhering more closely to the spec'd
algorithm[1] which addresses this situation by stipulating that a
scroll target whose scroll position has not yet been reached should
only be selected if it is within half a scroll port of the current
scroll position.

We have clarified that although the algorithm[1] is not presented as
normative at the moment, the intention is to make it normative at some
point in the future.

[1] https://drafts.csswg.org/css-overflow-5/#example-d2ca6884

Bug: 413645441
Change-Id: I620cfa8a06cbd4f8f904fdaaef250351110b56dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6505661
Commit-Queue: David Awogbemila <[email protected]>
Reviewed-by: Steve Kobes <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1455009}
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.

@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 4f6b0d0 into master May 2, 2025
21 checks passed
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-59f1b5ad7e branch May 2, 2025 17:13
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.

2 participants