Closed
Bug 537615
Opened 15 years ago
Closed 15 years ago
impossible to position cursor in text field
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec1.0+)
VERIFIED
FIXED
fennec1.0
Tracking | Status | |
---|---|---|
fennec | 1.0+ | --- |
People
(Reporter: blassey, Assigned: vingtetun)
Details
Attachments
(1 file, 1 obsolete file)
2.00 KB,
patch
|
mfinkle
:
review+
Gavin
:
review+
pavlov
:
superreview+
|
Details | Diff | Splinter Review |
If there is text in a text box with focus and you click some where in the middle of the text to reposition the cursor the text box will flash blue and then re-take focus with the cursor at the end of the text. The end result is its impossible to edit the text in a text box with out deleting everything after it. I see this on the samsung Omnia II, but I suspect its platform independent.
Reporter | ||
Updated•15 years ago
|
tracking-fennec: --- → ?
Reporter | ||
Comment 1•15 years ago
|
||
I see this on the n900 as well
Assignee | ||
Comment 2•15 years ago
|
||
yes, this is platform independent. The patch prevent setting the element to be set as the current element of FormHelper if it is already.
Assignee: nobody → 21
Attachment #420227 -
Flags: review?(mark.finkle)
Comment 3•15 years ago
|
||
Comment on attachment 420227 [details] [diff] [review] Patch >diff -r 24fa03e7ddac chrome/content/browser.js > if (FormHelper.canShowUIFor(element)) { >- FormHelper.open(element); >- return; >+ if (FormHelper.getCurrentElement() != element || gFocusManager.focusedElement != element) { >+ FormHelper.open(element); Could we move the currentElement check into FormHelper.open ? If aElement == currentElement just return Maybe the gFocusManager.focusedElement check could go there too Let me know what you think
Attachment #420227 -
Flags: review?(mark.finkle) → review-
Assignee | ||
Comment 4•15 years ago
|
||
Makes sense. We just need to return a boolean indicating if something has been done to know if we should prevent the default (mousedown/mouseup) action or not
Attachment #420227 -
Attachment is obsolete: true
Attachment #420241 -
Flags: review?(mark.finkle)
Updated•15 years ago
|
OS: Windows Mobile 6 Professional → All
Hardware: ARM → All
Updated•15 years ago
|
Attachment #420241 -
Flags: review?(mark.finkle) → review+
Updated•15 years ago
|
Attachment #420241 -
Flags: review?(gavin.sharp)
Updated•15 years ago
|
Attachment #420241 -
Flags: review?(gavin.sharp) → review+
Updated•15 years ago
|
Attachment #420241 -
Flags: superreview+
Updated•15 years ago
|
tracking-fennec: ? → 1.0+
Comment 5•15 years ago
|
||
https://hg.mozilla.org/mobile-browser/rev/7084ff222475
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → RC
Comment 6•15 years ago
|
||
Is there a test site where this works? I am still seeing the blue highlight whenever I tap on the editing text box even when its the current element (i.e. the cursor is blinking there).
Comment 7•15 years ago
|
||
verified FIXED on builds (I'm not a fan of the blue highlighting everytime I click on it though): Mozilla/5.0 (Windows; U; WindowsCE 5.2; en-US; rv:1.9.2b6pre) Gecko/20091228 Namoroka/3.6b6pre Fennec/1.0a4pre and Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2pre) Gecko/20100111 Firefox/3.6pre Fennec/1.1a1pre
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•