Closed Bug 1041221 Opened 10 years ago Closed 8 years ago

Selected text action bar items don't take precedence over previous text field

Categories

(Firefox for Android Graveyard :: Text Selection, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rnewman, Unassigned)

References

()

Details

Attachments

(1 file)

See screenshot.

Type in a field. Select some text in the page. Action bar appears, as expected... But with textfield options like save search engine, not text options like search/copy.
Yah that's extremely inconsistent ... TextSelection is fracked here as 1) There's a selection caret in the input field, and there's highlight text w/o handles on the page ... this looks similar to regression Bug 1030060 which we just-ish fixed ...

My STR there produced results that looked like: https://www.dropbox.com/s/us9egv3s35me8e7/regress1011059.png

Is this a current nightly? Do you have the page link?
2014-07-16 Nightly. 

Page added to bug.
Copying nchen...

This page does exhibit odd behavior ... I can identify a Google-keyboard issue (as noticed in the original bug), with the input fields that don't involve TextSelection ...

Usually if the keyboard state is corrupted, TextSelection can get confused, as it takes cues from messages generated by the IME.

However, the page may simply be foot-gunning itself and/or both sections of code.
fyi- Chrome handles this page properly.

STR on my N7 w/Google Keyboard:
   Open the example page, scroll down to field 3) Esas joyas
   Tap into the empty field, type |ttttt|
   Tap into the next empty field 4) Esos peinados
   -- Observe brief flash in field 3)
   Type |ttttt| where currently positioned in field 4)
   Tap at the end-of and into the previous field 3)
   -- Observe brief flash in field 4)
   Tap backspace ...
   Nothing happens until you type if 6 times, then the cursor jumps left between char-1 and char-2

Repeating with the Swift-keyboard does not reproduce the issue.

https://www.dropbox.com/s/6ox8nbvbm4v50tw/bug1041221-Settings-1.png
https://www.dropbox.com/s/d842ci8g5ode0bw/bug1041221-Settings-2.png
fwiw, this was with the Google keyboard on Nexus 10.
The new Gecko based selectionCarets we're implementing in bug 988143 seem to handle this in a more polished fashion

https://www.dropbox.com/s/u0mcn4ungdzc6t5/bug1041221.mp4?dl=0
Pruning some old bugs (part 2) either:
   ) obviated by new Core/Layout AccessibleCaret implementation in m-c and stable, targeted for 47.
   ) Or no longer being observable.

If you still see what you consider incorrect behaviour with the new version, please file a new bug targeted there, and attach a test-case or example link to help things :-)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: