Closed
Bug 1066024
Opened 10 years ago
Closed 10 years ago
Some high-DPI assets in GaiaGrid are incorrectly named
Categories
(Firefox OS Graveyard :: Gaia::Components, defect)
Tracking
(b2g-v2.0 wontfix, b2g-v2.1 fixed, b2g-v2.2 fixed)
RESOLVED
FIXED
2.1 S4 (12sep)
People
(Reporter: cwiiis, Assigned: cwiiis)
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
46 bytes,
text/x-github-pull-request
|
kgrandon
:
review+
bajaj
:
approval-gaia-v2.0-
bajaj
:
approval-gaia-v2.1+
|
Details | Review |
[Blocking Requested - why for this release]: (see below) High-DPI assets for shared components seem to all get bundled, instead of the correct one renamed during build. This can be seen if you look inside, say, the vertical home webapp zip and look at the images in the shared grid component - all of the suffixed images are bundled instead of just one at the correct resolution. This is mirrored in the app, where the unprefixed, low-dpi image will always be shown. Nominating this to block 2.1, as there are a number of high-dpi assets in shared components and this will not only make apps look worse than they should, but make them significantly larger too. I assume it's too late for 2.0(?)
Assignee | ||
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]: Didn't realise things could still block 2.0. I think this is critical enough that it should block 2.0 as it will make high-dpi devices look worse, but more critically, it will significantly increase the size of bundled apps (which is bad news for storage-limited devices).
blocking-b2g: 2.1? → 2.0?
Assignee | ||
Comment 2•10 years ago
|
||
urk, the bug isn't in the build system, the assets are missing the 'x' part of the suffix. This should probably still block, but probably doesn't affect quite as much thankfully :)
Component: Gaia::Build → Gaia::Components
Assignee | ||
Comment 3•10 years ago
|
||
I'll take this, this is just a simple renaming.
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•10 years ago
|
||
Doesn't hurt to get a look over this.
Attachment #8487888 -
Flags: review?(kgrandon)
Assignee | ||
Updated•10 years ago
|
Summary: High-DPI assets don't get bundled correctly for shared components → Some high-DPI assets in GaiaGrid are incorrectly named
Comment 5•10 years ago
|
||
Comment on attachment 8487888 [details] [review] Rename hi-dpi assets Doh, nice find! This makes me sad. Seems like we might want a linter for this.
Attachment #8487888 -
Flags: review?(kgrandon) → review+
Comment 6•10 years ago
|
||
In master: https://github.com/mozilla-b2g/gaia/commit/cb3464536a163aa14fceb90fa821c1eb20b7a7c9
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•10 years ago
|
||
Comment on attachment 8487888 [details] [review] Rename hi-dpi assets [Approval Request Comment] [Bug caused by] (feature/regressing bug #): Apps that use GaiaGrid may have some fuzzy icons and a larger app zip than necessary [User impact] if declined: Fuzzy icons and less on-board storage for the system [Testing completed]: Tested locally [Risk to taking this patch] (and alternatives if risky): Low risk, just a rename [String changes made]: None
Attachment #8487888 -
Flags: approval-gaia-v2.1?
Attachment #8487888 -
Flags: approval-gaia-v2.0?
Comment 8•10 years ago
|
||
Triage did not block on this as this does not appear to be a regression or has high impact to consider blocking, so this nice fix could get in 2.1 via approval given we are still taking low risk fixes there.
blocking-b2g: 2.0? → ---
Updated•10 years ago
|
Attachment #8487888 -
Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
Updated•10 years ago
|
Attachment #8487888 -
Flags: approval-gaia-v2.0? → approval-gaia-v2.0-
Comment 9•10 years ago
|
||
v2.1: https://github.com/mozilla-b2g/gaia/commit/b099878ed64ff0240d59783485d73f374b6b5931
status-b2g-v2.0:
--- → wontfix
Target Milestone: --- → 2.1 S4 (12sep)
Updated•10 years ago
|
Whiteboard: [systemsfe]
You need to log in
before you can comment on or make changes to this bug.
Description
•