Closed
Bug 1041293
Opened 10 years ago
Closed 6 years ago
Opt-out of italic font style for some locales in shared
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: timdream, Unassigned)
References
Details
(Keywords: l12y, Whiteboard: [FT:System-Platform][p=1])
Attachments
(1 file)
See bug 1023702.
Reporter | ||
Updated•10 years ago
|
Summary: Opt-out of italic font style for some locale → Opt-out of italic font style for some locale in shared/
Whiteboard: [FT:System-Platform][p=1]
Reporter | ||
Updated•10 years ago
|
Attachment #8459292 -
Flags: review?(kgrandon)
Reporter | ||
Updated•10 years ago
|
Summary: Opt-out of italic font style for some locale in shared/ → Opt-out of italic font style for some locales in shared
Comment 2•10 years ago
|
||
I'd prefer to have a single shared css variable for the font, and make that language dependent, and then use that variable instead of italic throughout?
Comment 3•10 years ago
|
||
Comment on attachment 8459292 [details] [review] mozilla-b2g:master PR#21962 I still think we should explore more options before going down this road, it doesn't look very maintainable to me. Will comment in bug 1023702.
Attachment #8459292 -
Flags: review?(kgrandon)
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #2) > I'd prefer to have a single shared css variable for the font, and make that > language dependent, and then use that variable instead of italic throughout? Well, I don't see putting a global variable in another file and rely on people remembering to include that file is in any way more maintainable. Initially I was thinking about using -moz-any() bug a warning in MDN says that there will be performance impact. I can surely use CSS variable to make the change less verbose but I object putting the variable in another shared file.
Comment 7•6 years ago
|
||
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.
Description
•