Re: [w3c/selection-api] Having a matching `selectend` event? (#146)

that will depend on what the user agent does currently to determine that selection/highlighting is done - i'm assuming browsers know when that's happening? at least for mouse this should be the case.

for mouse: user presses left mouse button down on selectable content, `selectstart` is fired. user drags the mouse and highlights/selects content, `selectionchange` is fired. user lefts go/releases left mouse button, they clearly ended their selection.

for touch, assume it's similar in terms of finger down, dragging/highlighting, then finger up (when UAs then often show contextual options/tooltips to copy etc). though i can see that then in cases where users are given controls to then manipulate the selection range may lead to further need for more `selectstart`/`selectend` for each operation where they drag the start/end markers.

keyboard (with caret type browsing) is probably the one case i can think of where it's indeed not unambiguous - but perhaps UAs could implement a heuristic that does the timer/debouncing internally and fires a `selectend` when IT believes selection is done?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/146#issuecomment-936378200