Closed Bug 881126 Opened 7 years ago Closed 7 years ago

[meta] Multiple device-pixel-density support for Gaia master and v1.1hd branch

Categories

(Firefox OS Graveyard :: Gaia, defect)

x86
macOS
defect
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: timdream, Assigned: timdream)

References

Details

This is the meta bug to track all multiple device-pixel-density support work.

Gaia on both master and v1.1hd branch should

-- support @1.5x and @2x devices through build script and high quality assets.
-- w/o any known layout defects.
-- looks good enough that everyone will be proud of our work :)

This bug can be considered fixed, and we shall rest.
Depends on: 885228
Tim, I think that bug 870311 should be on the dependency list here as well, but I don't want to disturb "your" tracker here, so I'll leave it up to you to add it :)
Hi guys wich approach are we going to take in order to add HD features to the homescreen app icons?
There are two ways:
- Create the blob at 1.5x size then scale down to 1 with css (possible fps lossy on homescreen panning)
- Using the hd canvas api (need to be implemented): https://bugzilla.mozilla.org/show_bug.cgi?id=780362
Flags: needinfo?(timdream)
Flags: needinfo?(rexboy)
(In reply to Ismael Gonzalez [:basiclines] from comment #2)
> Hi guys wich approach are we going to take in order to add HD features to
> the homescreen app icons?
> There are two ways:
> - Create the blob at 1.5x size then scale down to 1 with css (possible fps
> lossy on homescreen panning)
> - Using the hd canvas api (need to be implemented):
> https://bugzilla.mozilla.org/show_bug.cgi?id=780362

The blob approach sounds right from the engineering's POV, but I will get an answer on acceptance criteria. Thanks for bringing up :)
Flags: needinfo?(timdream)
Flags: needinfo?(rexboy)
Please see [GAIA_HD_ASSETS] whiteboard for pending assets; in the mean time this meta is done.

http://goo.gl/BsaRP
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.