Closed
Bug 902465
Opened 12 years ago
Closed 12 years ago
Too many CanvasLayer on e.me results hurt panning
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Firefox OS Graveyard
Gaia::Homescreen
Tracking
(blocking-b2g:leo+, b2g18 fixed, b2g-v1.1hd fixed)
RESOLVED
FIXED
blocking-b2g | leo+ |
People
(Reporter: vingtetun, Assigned: vingtetun)
References
Details
(Whiteboard: QARegressExclude)
Attachments
(3 files, 1 obsolete file)
1.92 KB,
patch
|
ranbena
:
review+
|
Details | Diff | Splinter Review |
5.33 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
1.76 KB,
patch
|
ranbena
:
review+
|
Details | Diff | Splinter Review |
Right now the e.me results are using canvas instead of DOM elements mostly for performance reasons while scrolling the results from top to bottom.
So each result on the screen is a canvas element.
Afaict each of those canvas results into a CanvasLayer that can not be merged into a bigger layer when scrolling from top to bottom or when panning between homescreen pages.
Replacing those canvas by img elements saves more than 5fps when panning. I have not measured while scrolling but it looks good too.
I would like to see that for 1.1 for even if it seems safe for Shortcuts I don't know the impact for Apps results.
Assignee | ||
Comment 1•12 years ago
|
||
The previous converts canvas to img and this one force all imgs to be rendered into the same layer instead of having one layer per row that is created/destroyed based on some gecko heuristic.
Assignee | ||
Comment 2•12 years ago
|
||
Better patch from evyatar once this stuff has been realized.
Attachment #786937 -
Attachment is obsolete: true
Attachment #787052 -
Flags: review+
Assignee | ||
Updated•12 years ago
|
Attachment #786984 -
Flags: review?(ran)
Assignee | ||
Comment 3•12 years ago
|
||
I think those 2 patches are harmless and improve the scrolling / panning experience of e.me.
I can live without it if this is really needed but that would be a shame. Those will land on master today and I recommend to land them on 1.1 if no regressions are found.
blocking-b2g: --- → leo?
Updated•12 years ago
|
Attachment #786984 -
Flags: review?(ran) → review+
Assignee | ||
Comment 4•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/2d143dd34f66a148106d915b8afd5d4641d219c1
https://github.com/mozilla-b2g/gaia/commit/2db7fc9697115575b942c92de3d32906adbdc3ef
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 5•12 years ago
|
||
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #3)
> I think those 2 patches are harmless and improve the scrolling / panning
> experience of e.me.
>
> I can live without it if this is really needed but that would be a shame.
> Those will land on master today and I recommend to land them on 1.1 if no
> regressions are found.
I think we should probably avoid this patch - feels like the risk/reward calculus doesn't really make sense here when the only issue is panning perf (not a regression from 1.0.1, I'm assuming).
Comment 6•12 years ago
|
||
Just to advocate for the patch- the issue is both panning performance and vertical scrolling, which we feel is crucial since shortcuts and apps are going to be in the user's face a lot of the time.
I agree the patch looks risky, since it touches 4 different files, but in essence there's no new logic introduced - only changing from canvas tags to img.
Assignee | ||
Comment 7•12 years ago
|
||
Unmerge while editing since it is a bit too expensive in this case.
Attachment #787492 -
Flags: review?(ran)
Comment 8•12 years ago
|
||
Is the performance a regression from 1.0.1 in any way? If not, this will land in 1.1. Please only renominate if this is perf regression instead of just a win.
blocking-b2g: leo? → -
Updated•12 years ago
|
Attachment #787492 -
Flags: review?(ran) → review+
Assignee | ||
Comment 9•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/e29b157a050033f87fa91fc2e932f4d2ac51046f
Last part. I strongly suggest to rethink the leo? flag since this will be in the user face all the time and this is the version that we have given to QA folks...
blocking-b2g: - → leo?
Assignee | ||
Comment 10•12 years ago
|
||
(In reply to Alex Keybl [:akeybl] from comment #8)
> Is the performance a regression from 1.0.1 in any way? If not, this will
> land in 1.1. Please only renominate if this is perf regression instead of
> just a win.
I don't think you should consider regression as the only criteria here. A bug in a part of the UI never used does not matter, a bug in a part of the UI that is the first thing we shown to user matters a bit much.
Comment 11•12 years ago
|
||
Paris triage: leo+. the difference is quite big before and after the patch. Since this is now the center of the homescreen, user experience on this should weight more
blocking-b2g: leo? → leo+
Comment 13•12 years ago
|
||
v1.1.0hd: a3612a020f3a85cc3cea0cd46714b44218b55f0c
v1.1.0hd: 7273a22f41c4e39912cb40c4f8ed2f14f16529ae
v1.1.0hd: f4231bc2ff87b3a43437b98b538fb01cf978d4b3
status-b2g-v1.1hd:
--- → fixed
Updated•12 years ago
|
Whiteboard: QARegressExclude
Updated•11 years ago
|
Assignee: nobody → 21
You need to log in
before you can comment on or make changes to this bug.
Description
•