[Keyboard][V2.0] [Flame] Cursor appears at the beginning of string when clicked on top of text field.




4 years ago
7 months ago


(Reporter: mukeshk1990, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [LibGLA,TD112744,QE3,B])


(1 attachment)



4 years ago
[Title]Cursor appears at the beginning of string when clicked on top of text field.
1.open SMS or Contact or Calendar
2.Click on any text field
3.Type a string say "abcdefgrhu"
4. Press on top of that text field

Actual: The cursor appears at the beginning of the string

Expected: The cursor should not appear at the beginning of the string

Build: 20141017101840


4 years ago
Flags: needinfo?(rlu)
Whiteboard: [LibGLA,TD112744,QE3,B]
What's the expected result?

I think it depends on where you clicked on the input field.
If you clicked near the end of the input field, the cursor would appear at the end.

After v2.1, we would have a caret handler for easier cursor movement.
Flags: needinfo?(rlu)
Change the component as bug 924692.
Component: Gaia::Keyboard → Selection
Product: Firefox OS → Core

Comment 3

4 years ago
Lets say we type  "abcdefghijklmnopq" in text field .Normally when touch on any character(eg. 'd' the cursor will changed to the postion after that character d). But this issue  tells the scenario where the user touches on the top border of textfield or little above, the cursor position is changed to the beginning of the string.

Comment 4

4 years ago
When we touch on editor box , the dom input sends both Focus and the Mouse events which updates the cursor position .But when we touch on the border or outside,it  sends only focus event to application and since it doesn't have the selection information, it always reset to the beginning of the editor.


4 years ago
Flags: needinfo?(ryang)
We can't reproduce the bug on Flame 2.0.

Could you please provide the video for this bug to make ti clear ?

Thanks !
Flags: needinfo?(ryang)

Comment 6

4 years ago
Created attachment 8512598 [details]
THe reproduction steps

PLease see the attached video .


4 years ago
Flags: needinfo?(ryang)
Hi Rudy, would you please kindly check this ? 
Thank you very much !!
Flags: needinfo?(ryang) → needinfo?(rlu)
Doesn't look like a blocker to me.

But anyway, the selection behavior is controlled by Gecko.


I heard that you have handled the text selection issues, do you know if we have already addressed this kind of issues before?
Thank you.
Flags: needinfo?(rlu) → needinfo?(tlin)
This behavior is the same as the Firefox browser, and Google chrome has the same behavior. On B2G 2.2, we will have touch-caret to make it easier to move cursor.
Flags: needinfo?(tlin)
Closing as we are not working on Firefox OS anymore.
Last Resolved: 7 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.