Closed Bug 821497 Opened 12 years ago Closed 12 years ago

Selected text is only highlighted when panning

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Version:
20 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bug.zilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121206 Firefox/20.0
Build ID: 20121206030737

Steps to reproduce:

Long pressed to select text. Galaxy Note, CM10 (4.1.2)


Actual results:

Selected text is not highlighted in orange. It's only highlighted once you pan.


Expected results:

Selected text should be highlighted in orange.
Same device, same build Android 4.0.4; works for me.
Must be a profile issue. Closing for now.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Unfortunately this persists, now I am unable to select any text at all by long pressing. I have tried a new profile and a clean installation. This is on a Galaxy Note on CM10 (4.1.2).

Can anyone replicate?
This is still an issue on a Galaxy Note (4.1.2), even with a new profile. Works the first couple of times and then cannot highlight text. Once I pan up or own then the text is highlighted.
Can someone please reply to confirm or otherwise this bug with a Galaxy Note on 4.1.2? It still happens on my device.
Works for me on my Note (Android 4.0.4, ICS) (sample site I used with really basic text was http://kernel.org), tried release mozilla-17 and Beta mozilla-18; perhaps this is a CyanogenMod issue. Which URLs are problematic for you?
Resolution: INVALID → WORKSFORME
typo (meant 18, and 19 above)
Hi, it's not site specific. To be honest it's not that big an issue for me. The text is highlighted when I pan up / down.

I'm happy to put this down to Cyanogenmod and close this - just wanted to highlight it.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.