Closed
Bug 994733
Opened 12 years ago
Closed 10 years ago
Text selection handles should snap to character and line breaks
Categories
(Firefox for Android Graveyard :: Text Selection, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: snorp, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
|
13.89 KB,
patch
|
wesj
:
feedback+
|
Details | Diff | Splinter Review |
When dragging the selection handles around, I don't think they should float freely. Instead, they should snap to character and line breaks (like other handles on Android).
Comment 1•11 years ago
|
||
If I recall correctly, this bug was about how we differ from Chrome when selecting text in input elements. We allow the user to drag the UI handles around the screen, outside the editable, though we confine the actual text selection to the editable contents. On handle release, we snap the handle back to the right place.
This rough WIP contricts the handle positions internal to the editable as Chrome, Browser, etc. does.
Attachment #8494613 -
Flags: feedback?(wjohnston)
Updated•11 years ago
|
Attachment #8494613 -
Attachment is obsolete: true
Attachment #8494613 -
Flags: feedback?(wjohnston)
Comment 3•11 years ago
|
||
Comment on attachment 8494620 [details] [diff] [review]
bugHandles.diff
Review of attachment 8494620 [details] [diff] [review]:
-----------------------------------------------------------------
I worry a bit about making this "synchronous", but it seems to work well. Happy to give it a ride.
::: mobile/android/base/TextSelectionHandle.java
@@ +136,5 @@
> +
> + // If we're positioning a cursor, don't move the handle here. Gecko
> + // will tell us the position of the caret, so we set the handle
> + // position then. This allows us to lock the handle to wherever the
> + // caret appears.
I don't think this comment is correct anymore.
Attachment #8494620 -
Flags: feedback?(wjohnston) → feedback+
Comment 4•10 years ago
|
||
Pruning some old bugs obviated by new Core/Layout AccessibleCaret implementation, or being no longer observable.
(Please re-open if appropriate.)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•