Closed
Bug 913397
Opened 11 years ago
Closed 11 years ago
[Keyboard] Make keyboard app support 1.5x graphics
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(blocking-b2g:koi+, b2g-v1.2 fixed)
People
(Reporter: lchang, Assigned: lchang)
References
Details
Attachments
(1 file)
We will get a new look of the pinyin IME after Bug 900907 land. Do we need 1.5x graphics for the assets we added in that patch?
Comment 1•11 years ago
|
||
Please help test the new UX introduced by Bug 900907 on hd device, like helix or S2 and see if all the graphics is ok. Thanks.
Assignee | ||
Updated•11 years ago
|
Summary: [Keyboard] Do we need 1.5x graphics for the pinyin IME? → [Keyboard] Make keyboard app support 1.5x graphics
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #806398 -
Flags: review?(rlu)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → lchang
Updated•11 years ago
|
blocking-b2g: koi? → koi+
Comment 3•11 years ago
|
||
Luke, Any updates with this bug? Who else do we need a review from?
Flags: needinfo?(lchang)
Assignee | ||
Comment 4•11 years ago
|
||
Hi Preeti, I'm waiting for Rudy's review. Hi Rudy, Do you have any update for this patch, thanks.
Flags: needinfo?(lchang) → needinfo?(rlu)
Comment 5•11 years ago
|
||
Comment on attachment 806398 [details]
Pull Request
r+, with the CSS unit should be in 'rem'.
Thanks.
Attachment #806398 -
Flags: review?(rlu) → review+
Comment 6•11 years ago
|
||
Sorry for the delay. I don't have a chance to test this on device, please help make sure it looks OK on WVGA device. Thanks.
Flags: needinfo?(rlu)
Assignee | ||
Comment 8•11 years ago
|
||
travis passed: https://travis-ci.org/mozilla-b2g/gaia/builds/12555016 merged in gaia master: https://github.com/mozilla-b2g/gaia/commit/17e871ae1f82699793e3cd28acda805ba724a8b6
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(rlu)
Resolution: --- → FIXED
Comment 9•11 years ago
|
||
Uplifted 17e871ae1f82699793e3cd28acda805ba724a8b6 to: v1.2: 3e34df22eaa1d75225f55deae79ce96e50cd7823
status-b2g-v1.2:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•