Closed Bug 871960 Opened 11 years ago Closed 6 years ago

b2g/chrome/content/content.css shouldn't use hard coded colours

Categories

(Firefox OS Graveyard :: General, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mounir, Unassigned)

References

Details

Attachments

(1 file, 1 obsolete file)

'color' properties in content.css should use system wide colours for text/background colours -moz-textField. That would allow customisation of the colours (like themes), make sure to pass reftests and would make a11y easier for visually impaired users (like having high contrast themes).
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → All
I can't find -moz-textField. Do you mean -moz-FieldText instead?
(In reply to jwwang from comment #1)
> I can't find -moz-textField. Do you mean -moz-FieldText instead?

Yes. -moz-Field and -moz-FieldText.
Assignee: nobody → jwwang
Status: NEW → ASSIGNED
Attachment #752503 - Flags: review?(mounir)
Comment on attachment 752503 [details] [diff] [review]
replace hard coded colors with -moz-FieldText

Review of attachment 752503 [details] [diff] [review]:
-----------------------------------------------------------------

Given that layout/style/forms.css should already set the value of 'color' properties, I guess you can simply remove them. Also, you should ask :vingtetun for a revieew. This is directly affecting Gaia and he knows more than I do why those were hardcoded values.
Attachment #752503 - Flags: review?(mounir)
Comment on attachment 753086 [details] [diff] [review]
remove hard coded colors in content.css and duplicated definitions in forms.css

Given that this color naming scheme is not yet working I would like to see bug 849223 fixed first. 

Then defining those colors to #414141 in b2g/app/b2g.js would be nice too for this patch. r- because of this and the fact that it can't work without bug 849223.

I like the removal of the overridden colors.
Attachment #753086 - Flags: review?(21) → review-
Btw, will this color extraction (from forms.css to content.css) fail if forms.css is running on some other platform where it doesn't inherit from b2g/chrome/content/content.css?
Release the bug so someone can take it.
Assignee: jwwang → nobody
Status: ASSIGNED → NEW
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: