Closed
Bug 673297
Opened 13 years ago
Closed 5 years ago
Text selection arrows are not native
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mounir, Unassigned)
References
Details
(Keywords: parity-opera)
The arrows used to select some text in a page looks native on my phone (Nexus S, so Android 2.3) but are far from that on my tablet (Android 3.1 I believe). I guess that the arrows appearance is hard coded to look like the ones in Android 2.3. Can't we use the applied theme instead?
Comment 1•13 years ago
|
||
(In reply to comment #0) > I guess that the arrows appearance is hard coded to look like the ones in > Android 2.3. Can't we use the applied theme instead? No, we can't. We can only supply renderings with our own themes (we have 3 currently)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > (In reply to comment #0) > > > I guess that the arrows appearance is hard coded to look like the ones in > > Android 2.3. Can't we use the applied theme instead? > > No, we can't. We can only supply renderings with our own themes (we have 3 > currently) What do you mean? Our code currently doesn't allow us to use to do that? or it's just technically impossible.
Comment 3•13 years ago
|
||
Android does not, to my knowledge, give us access to the images.
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to comment #3) > Android does not, to my knowledge, give us access to the images. On Opera Mobile, it seems to work as expected. If Android doesn't let us access to the images, can't we at least do a runtime check and show different arrows?
Reporter | ||
Updated•13 years ago
|
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Whiteboard: [parity-opera]
Comment 5•6 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-opera
Whiteboard: [parity-opera]
Comment 6•5 years ago
|
||
Closing all opened bug in a graveyard component
Status: REOPENED → RESOLVED
Closed: 13 years ago → 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•