Closed
Bug 602666
Opened 15 years ago
Closed 7 years ago
Clicking on an input field into the chrome UI should move the caret under the mouse position
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: vingtetun, Unassigned)
Details
Bug 592330 prevent input field to steal the focus during a mousedown, while we don't have the confirmation that the user intentionally click on it.
As a side effect, this prevent the caret to be positioned during the mousedown and to be at the right place during a mouseup.
Comment 1•15 years ago
|
||
Build ID: Mozilla /5.0 (Android;Linux armv7l;rv:2.0b12pre) Gecko/20110210 Firefox/4.0b12pre Fennec /4.0b5pre
Device: Motorola Droid 2 (Android 2.2), Samsung Galaxy S Captivate (Android 2.1 update 1)
Steps to reproduce:
1. Visit http://people.mozilla.com/~tchung/html_tp/formsninputv2.html
2. Click in the text area box.
3. Move the caret somewhere between the characters of the string.
Actual results:
After step 2, the page is zoomed in to the text area box, the VKB pops up BUT the caret is not visible to the user. The user has to resize the page (zoom out) to see the caret. After zooming out, the caret becomes visible but it does not flicker, so again, the caret cannot be positioned during tapping. One has to zoom in / zoom out / zoom in /zoom out to have focus during tapping.
Expected results:
The caret should be visible to the user and gave focus during tapping.
Comment 2•14 years ago
|
||
Related I presume in Firefox Beta on Android
1. search for something in Google
2. click the search text box to edit the search text
At this point the caret is visible and flashing but left/right input via the optical mouse (HTC Desire) has no effect on the position of the caret. This makes it very difficult to edit the text. Note that up/down input causes focus to shift to the previous/next input.
The expected behaviour is for mouse left/right input to move the caret in the text box.
Comment 3•7 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•