As we've landed the patches from https://bugzilla.mozilla.org/show_bug.cgi?id=83064 There is a few issues related with missing images, and some visual tweaks that should be fixed in order to close the work done to support multi-resolution in Gaia.

We are waiting to receive updated @2x assets from Sergi. But we can start with the code review

Comment on attachment 747923 [details] Polishing PR Looks good. But we shouldn't be touching Message app this week I think (given the fact they are working hard on MMS work).

Comment on attachment 747923 [details] Polishing PR looks good as the issue on github has been resolved. Thank you!

The changes about sms should not be related with the work done with MMS. Anyway i will wait to talk with Borja to confirm it. Thx!

I assumed after the last huge multi resolution bug that we would split these into seperate PR's per application?

Hey Dale, this is going to be the only patch that we will land for this bug (then close). Will not be like the multi resolution one. But yes is way more easy to handle it in one PR as all changes are small fixes and missing images.

Comment on attachment 747923 [details] Polishing PR The scrubber in the video player still has an issue with a background gradient that doesnt reach the full height on high resolution devices. I am happy to r+ this as it isnt a regression and we can fix in a follow up. (needs rebased)

Actually testing this on the unagi, it is a regression, the scrubber should be fixed before this is merged, but seeing the size of the PR happy for you to merge it once you have rebasd / fixed / tested. Cheers

Sure Dale i'll work on it! Thx!

Merged in master: https://github.com/mozilla-b2g/gaia/commit/ca0af90cf372af3dff159e5cd140f5fa4c1620c4

(In reply to Ismael from comment #10) > Merged in master: > https://github.com/mozilla-b2g/gaia/commit/ > ca0af90cf372af3dff159e5cd140f5fa4c1620c4 This has created a regression in clock performance on . Can you back-out the clock part (or I will backout all the PR ;)). See https://datazilla.mozilla.org/b2g/?branch=master&device=unagi&range=7&test=cold_load_time&app_list=clock&app=clock&gaia_rev=66f3098da13467b4&gecko_rev=52341e43539a0e8b

Checking it right now! Should i create a new bug and PR for fixing it?

The Gaia revision that you are providing (66f3098da13467b4) is not the same as the generated for this PR (ca0af90cf372af3dff159e5cd140f5fa4c1620c4). In fact this patch reduces load time by 30ms: https://datazilla.mozilla.org/b2g/?branch=master&device=unagi&range=7&test=cold_load_time&app_list=clock&app=clock&gaia_rev=ca0af90cf372af3d&gecko_rev=39c9d5a5c09dfb94

(In reply to Ismael from comment #13) > The Gaia revision that you are providing (66f3098da13467b4) is not the same > as the generated for this PR (ca0af90cf372af3dff159e5cd140f5fa4c1620c4). > In fact this patch reduces load time by 30ms: > https://datazilla.mozilla.org/b2g/ > ?branch=master&device=unagi&range=7&test=cold_load_time&app_list=clock&app=cl > ock&gaia_rev=ca0af90cf372af3d&gecko_rev=39c9d5a5c09dfb94 I copy the wrong revision number but looking at: https://datazilla.mozilla.org/b2g/?branch=master&device=unagi&range=7&test=cold_load_time&app_list=clock&app=clock The last commit in this app since days (weeks?) is this one so it seems deeply related to me :) (In reply to Ismael from comment #12) > Checking it right now! > Should i create a new bug and PR for fixing it? please.

I still don't see the problem on that graphs (i'm not too much familiar with perf-o-matic). What i see is a variety of commits that introduced slower cold-load-times: 66f3098da13467b4 = 2013-05-24 - 861.87ms - not related with clock app ? 7c52767685ab0fe7 = 2013-05-27 - 1000.33 - not related with clock app ? Then i see my commit that actually speed up from 880.67ms to 851.83ms: ca0af90cf372af3d = 2013-05-27 - 851.83 - Polish bug (clock app changes) Am i missing something?

Does this need to be included in leo+ ?

I dont think so as 830644 is not supposed to be nominated to leo

This bug should not be nominated to leo? as it depends on #830644 which has to land only from v1.2

Please be informed that we did a JS-based responsive design in keyboard app, so it is not required to include shared/style/responsive.css for keyboard app. Including it may cause incorrect layout on qHD/WVGA resolution, like Bug 874778.

Based on comment 18 , moving leo ? -> koi?