Closed Bug 662978 Opened 9 years ago Closed 9 years ago
About:Config is hard to read for the Add a New Preferences with the Gingerbread theme
1. on an Android 2.3 device go to About:config Expected: it's easy to read the first line ( Add a New Preferences ) Actual: White on light grey is hard to read.
Mozilla/5.0 (Android; Linux armv71; rv7.0a1) Gecko/20110608 Firefox/7.0a1 Fennec/7.0a1 Device: HTC Flyer OS: Android 2.3
Note: also note, in portrait mode, the text boxes for adding a string is slightly off from each other.
Summary: About:Config is hard to read for the selected option with the Gingerbread theme → About:Config is hard to read for the Add a New Preferences with the Gingerbread theme
9 years ago
tracking-fennec: --- → ?
Assignee: nobody → lucasr.at.mozilla
tracking-fennec: ? → -
Comment on attachment 549211 [details] [diff] [review] Set newpref label color to black This seems like a good fix for core and will be inherited by gingerbread. We want 'black' in all themes and this makes that happen.
Attachment #549211 - Flags: review?(mark.finkle) → review+
Landed on mozilla-inbound: http://hg.mozilla.org/integration/mozilla-inbound/rev/d19168e0fe63 In the future, it's best if you can attach a patch with author & checkin-message already set, as described here: https://developer.mozilla.org/en/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3f
(In reply to comment #5) > Landed on mozilla-inbound: > http://hg.mozilla.org/integration/mozilla-inbound/rev/d19168e0fe63 > > In the future, it's best if you can attach a patch with author & > checkin-message already set, as described here: > https://developer.mozilla.org/en/ > Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check- > in_for_me.3f Ok, I'll update my other pending patches tomorrow. Thanks for the info, Daniel.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 8
Verified Fixed Mozilla/5.0 (Android; Linux armv7l; rv:8.0a1) Gecko/20110802 Firefox/8.0a1 Fennec/8.0a1
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.