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

Update the-input-element/selection-pointer.html to support multi-range #39753

Merged
merged 1 commit into from
Apr 28, 2023

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Apr 28, 2023

See [1] for context. This CL makes this test pass in the case that
multiple range support is present and selecting across an \<input>
creates multiple ranges. Note that in my local testing, only a single
range is created on all rendering engines (Blink, WebKit, and Gecko)
when the user selects across an \<input>. Thus, I was not able to test
the newly added code here. I did attempt to verify that it would work
correctly, however, and I believe it will.

[1] web-platform-tests/interop#313

Change-Id: I88c88fcca47da627a0be9de518b76bbbcc07964b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4492089
Reviewed-by: Di Zhang <dizhangg@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1137412}

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.

See [1] for context. This CL makes this test pass in the case that
multiple range support is present *and* selecting across an `<input>`
creates multiple ranges. Note that in my local testing, only a single
range is created on all rendering engines (Blink, WebKit, and Gecko)
when the user selects across an `<input>`. Thus, I was not able to test
the newly added code here. I did attempt to verify that it would work
correctly, however, and I believe it will.

[1] web-platform-tests/interop#313

Change-Id: I88c88fcca47da627a0be9de518b76bbbcc07964b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4492089
Reviewed-by: Di Zhang <dizhangg@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1137412}
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 655997d into master Apr 28, 2023
14 of 18 checks passed
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-4492089 branch April 28, 2023 22:11
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

2 participants