Selection interface functions should not move focus |
|||||||||||||
Issue description
Implementation of Selection#collapse,collapseTo{Start,End}, extend() call
FrameSelection::setSelection() without DoNoSetFocus option. This means these
API calls move focus to new selected element.
The spec[1] doesn't specify this behavior and Edge and Firefox don't do this,
see [2] for reproduce.
[1] https://www.w3.org/TR/selection-api/#dom-selection-collapse
[2] https://jsfiddle.net/b394qq37/1/
,
Feb 9 2017
I confirmed that removeAllRange() on focused contenteditable element removed a caret without removing focus in Firefox.
,
Feb 9 2017
,
Feb 23 2017
This is the root cause of Issue 695211.
,
Feb 24 2017
,
Feb 24 2017
This is a canceled CL: https://codereview.chromium.org/2709983005
,
Feb 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/beb1e82fe0893056ca1ffb9c729dc8f52cf2f30b commit beb1e82fe0893056ca1ffb9c729dc8f52cf2f30b Author: tkent <tkent@chromium.org> Date: Tue Feb 28 09:02:21 2017 Selection API: Add a UseCounter for focus change by selection change. BUG=690272 Review-Url: https://codereview.chromium.org/2718293002 Cr-Commit-Position: refs/heads/master@{#453548} [modify] https://crrev.com/beb1e82fe0893056ca1ffb9c729dc8f52cf2f30b/third_party/WebKit/Source/core/editing/DOMSelection.cpp [modify] https://crrev.com/beb1e82fe0893056ca1ffb9c729dc8f52cf2f30b/third_party/WebKit/Source/core/frame/UseCounter.h
,
Mar 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c608fa61bc66ef930ee8902f2d154b4d4fd6e7ed commit c608fa61bc66ef930ee8902f2d154b4d4fd6e7ed Author: tkent <tkent@chromium.org> Date: Wed Mar 01 06:39:23 2017 Selection API: Add a UseCounter for focus change by Selection.modify(). This is a leftover of https://codereview.chromium.org/2718293002/. BUG=690272 Review-Url: https://codereview.chromium.org/2727553002 Cr-Commit-Position: refs/heads/master@{#453867} [modify] https://crrev.com/c608fa61bc66ef930ee8902f2d154b4d4fd6e7ed/third_party/WebKit/Source/core/editing/DOMSelection.cpp
,
Mar 6 2017
,
Mar 6 2017
,
Mar 15 2017
We need to wait until the UseCounter reaches to Stable.
,
Mar 15 2017
,
May 21 2017
https://www.chromestatus.com/metrics/feature/timeline/popularity/1837 Next step: Make a chromestatus.com entry, and send intent-to-remove
,
Jun 28 2017
> Next step: Make a chromestatus.com entry, and send intent-to-remove Done: https://www.chromestatus.com/feature/5335417998016512 Next step: Send intent-to-deprecate-and-remove to blink-dev.
,
Jul 12 2017
I withdrew the intent. At least addRange() and selectAllChildren() set focus with all major browsers. We should check other functions, and update the Selection API specification.
,
Oct 4 2017
,
Oct 4
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by yosin@chromium.org
, Feb 9 2017