Explainer for Multi-Range Selection in Chromium#1311
Open
sambandaru wants to merge 2 commits into
Open
Conversation
utpathak
reviewed
Apr 30, 2026
utpathak
reviewed
Apr 30, 2026
utpathak
reviewed
Apr 30, 2026
sambandaru
force-pushed
the
multi-range-selection
branch
2 times, most recently
from
9a67e2d to
c24283b
Compare
sambandaru
force-pushed
the
multi-range-selection
branch
from
c24283b to
b8ba5f7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an explainer proposing multi-range selection support in W3C Selection API spec. The spec currently mandates that addRange() no-ops when a range already exists (rangeCount capped at 1). This proposes allowing addRange() to accumulate disjoint ranges, enabling Ctrl+Click discontinuous text selection. Chromium is pursuing implementation; Gecko already ships this behavior.