Explainer for Multi-Range Selection in Chromium#1311
Conversation
sambandaru
force-pushed
the
multi-range-selection
branch
3 times, most recently
from
c24283b to
b8ba5f7
Compare
sambandaru
force-pushed
the
multi-range-selection
branch
3 times, most recently
from
9c8f1de to
13c21d7
Compare
sambandaru
force-pushed
the
multi-range-selection
branch
from
13c21d7 to
3b06b9c
Compare
mhochk
left a comment
mhochk
left a comment
There was a problem hiding this comment.
LGTM to get the discussion going. I left a handful of comments but none are blocking. Let me know if/when you want this merged to main.
dandclark
left a comment
dandclark
left a comment
There was a problem hiding this comment.
LGTM with some small things.
Are there any Alternatives Considered that can be added here? One might be adding browser UI that would allow layout selection without updating the DOM APIs. That was done at one point in Edge with the Web Select feature, which has since been removed: https://onlinecomputertips.com/support-categories/windows/enable-web-select-microsoft-edge/
sambandaru
force-pushed
the
multi-range-selection
branch
from
dfc46ea to
fcf0e07
Compare
|
@mhochk and @dandclark |
I have added this and custom overlays as considered alternatives. |
|
@mhochk / @dandclark |
4 participants
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.