Closed
Bug 627189
Opened 15 years ago
Closed 13 years ago
Add-ons are using wrong font family and text color
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: limi, Assigned: zer0)
Details
Attachments
(1 file)
It looks like add-ons created using the Jetpack SDK are using a serif font as their default, making elements added to the add-ons bar look out of place.
To ensure consistent look across Win7/Vista, XP and OS X respectively, the font should be:
font-family: "Segoe UI", Tahoma, "Lucida Grande", sans-serif;
You can see this in the Hard Blocker add-on (although he might have added CSS to correct this by the time I have filed this bug ;):
https://addons.mozilla.org/en-US/firefox/addon/hard-blockers-counter/
Not sure if there's a standard on Linux, but I assume sans-serif may take care of that.
Comment 1•15 years ago
|
||
you can just test the revision 256: https://builder.addons.mozilla.org/addon/1000065/revision/256/
Reporter | ||
Comment 2•15 years ago
|
||
Added screenshot from OS X to illustrate.
Comment 3•15 years ago
|
||
The text color isn't inherited from the toolbar either. Can be tested with a persona with a text color other than black.
OS: Mac OS X → All
Hardware: x86 → All
Updated•14 years ago
|
Priority: -- → P2
Target Milestone: --- → 1.0
Updated•14 years ago
|
Summary: Add-ons are using wrong font family → Add-ons are using wrong font family and text color
Comment 4•14 years ago
|
||
(automatic reprioritization of 1.0 bugs)
Priority: P2 → P1
Target Milestone: 1.0 → 1.1
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → zer0
Updated•14 years ago
|
Priority: P1 → P2
Instead of hardcoding anything, can these values be picked up from the application itself?
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.1 → ---
Assignee | ||
Comment 7•13 years ago
|
||
Fixed by dglol in this commit: https://github.com/mozilla/addon-sdk/commit/da8fc9b60a6ecc668194d15d5d624587e3c18208
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•