Closed
Bug 698131
Opened 14 years ago
Closed 14 years ago
Highlight for the Awesome page should be something other than solid white
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: nhirata, Assigned: lucasr)
Details
Attachments
(2 files)
78.37 KB,
image/png
|
Details | |
2.07 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
1. click in the url bar
2. tap and hold on a URL in the all pages.
Expected: highlight should be something of a highlight and not solid white
Actual: solid white; can't see the text beneath it.
(see third line in the screenshot)
Comment 1•14 years ago
|
||
There is no selection on items thus far. My suspicion is that that entry is merely a dud entry missing it's title.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → lucasr.at.mozilla
Comment 2•14 years ago
|
||
I think this is the same issue in another bug I filed over the weekend, bug 698223 (please dupe if that's the case)
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #2)
> I think this is the same issue in another bug I filed over the weekend, bug
> 698223 (please dupe if that's the case)
It looks like a different issue.
Assignee | ||
Comment 4•14 years ago
|
||
Attachment #570983 -
Flags: review?(mark.finkle)
Comment 5•14 years ago
|
||
Comment on attachment 570983 [details] [diff] [review]
Always use white style list views in AwesomeBar
Nice. This means we should be using system standard colors for selection, focus and whatever else, but still be using a white background in the lists.
Attachment #570983 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 6•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 7•14 years ago
|
||
20111103040334
http://hg.mozilla.org/projects/birch/rev/c09a52af4cd8
Samsung Nexus S (Android 2.3.6)
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•