Closed
Bug 1069495
Opened 11 years ago
Closed 7 years ago
[Fonts] When shallow flashing kk, new fira fonts are not utilized.
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pbylenga, Unassigned)
References
Details
Attachments
(1 file)
|
288.62 KB,
image/png
|
Details |
Description:
When we shallow flash (Gaia + Gecko) on top of v180 we don't utilize fira fonts. I can confirm they still exist in /system/fonts when flashed with this method. This does not occur on the base image v180 by itself or when we full flash.
Repro Steps:
1) Update a Flame to 20140917123004 using Shallow Flash (Gaia + Gecko only)
2) Observe font in FTU
Actual:
Fonts aren't the new Fira fonts
Expected:
Fonts are the new Fira fonts
Environmental Variables:
Device: Flame v2.1
Build ID: 20140917123004
Gaia: ad374f4b2a07cb5711679322a815f9feadb5cf64
Gecko: b4d5f9314661
Version: 34.0a2 (2.1)
Firmware Version: v180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Repro frequency: 10/10 100%
See attached: screenshot
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
Michael - Is there anything in the fullflash script (https://raw.githubusercontent.com/nhirata/fullflash/master/flash_Gg.sh) that could causing this to happen?
Flags: needinfo?(mwu)
Comment 3•11 years ago
|
||
No. But it looks like you probably didn't install the updated fonts. 2.1 uses a new name for Fira (Fira Sans now, instead of Fira Sans OT) so you have to install updated fonts to see any Fira fonts. I have a font update package at https://people.mozilla.org/~mwu/fira-font-update.zip
Flags: needinfo?(mwu)
Comment 4•11 years ago
|
||
Peter - Can you try testing the font update package in comment 3?
Flags: needinfo?(pbylenga)
| Reporter | ||
Comment 5•11 years ago
|
||
The issue does not reproduce when I install the fonts manually with the update package.
Flags: needinfo?(pbylenga)
Comment 7•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•