Closed
Bug 796239
Opened 13 years ago
Closed 12 years ago
[Task Manager] Should use transform instead of scrollLeft
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Firefox OS Graveyard
Gaia::System
Tracking
(blocking-b2g:-, blocking-basecamp:-, b2g18+)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
b2g18 | + | --- |
People
(Reporter: ghtobz, Unassigned)
References
Details
(Keywords: perf, Whiteboard: UX-P5)
Attachments
(1 file)
160 bytes,
text/html
|
timdream
:
review+
vingtetun
:
approval-gaia-v1-
|
Details |
[GitHub issue by timdream on 2012-09-05T21:22:06Z, https://github.com/mozilla-b2g/gaia/issues/4370]
Very bad performance.
[GitHub comment by timdream on 2012-09-16T18:17:07Z]
Although scrolling generates bands on repaint area, the performance is not that bad. Closing as invalid.
[GitHub comment by cgjones on 2012-09-17T18:46:54Z]
This still a valid issue that needs to be fixed.
[GitHub comment by autonome on 2012-09-17T22:30:40Z]
/cc @michalbe
[GitHub comment by timdream on 2012-09-18T05:24:05Z]
@cgjones Fair enough.
Comment 5•13 years ago
|
||
We're trying to understand the criticality of this blocking-basecamp+ issue. What's the user impact here?
This is needed to reliably hit the perf target for this bit of UI.
blocking-basecamp: + → ?
Comment 7•13 years ago
|
||
Acording to what :vingtetun said, scrolling works way better than transforms eg. in Settings or Gallery. Do we really want to rebuild cardsview?
Those are different use cases than here.
I reset to blocking? so that we can reevaluate priority based on field testing.
Comment 9•13 years ago
|
||
Blocking because of performance. We can re-prioritize or unblock when triaging later.
blocking-basecamp: ? → +
Priority: -- → P2
Panning in the Cards View looks OK here at the moment (on the Otoro). Can you give exact STR or some way to measure the performance against a concrete target?
Comment 11•13 years ago
|
||
Malina, what is the status of eideticker/b2g, could we measure the framerate on this?
Flags: needinfo?(mdas)
Comment 12•13 years ago
|
||
(In reply to JP Rosevear [:jpr] from comment #11)
> Malina, what is the status of eideticker/b2g, could we measure the framerate
> on this?
[ I'll jump in here, since I'm the main contact for B2G/Eideticker now; mdas may have more information ]
We have eideticker "working", minus some flakiness and bugs in the support for handling gestures (which may be fixed by bug 801578).
The key for being able to measure something like this through eideticker would be being able to reproduce the test case in question. To that end, I guess my questions would be:
1. What is this card view?
2. Is there a way to get to the screen with this card view programatically? (e.g. through marionette)
3. What gesture/action do we need to produce in order to reproduce the performance issue? (if there is one)
Comment 13•13 years ago
|
||
(In reply to William Lachance (:wlach) from comment #12)
> (In reply to JP Rosevear [:jpr] from comment #11)
> > Malina, what is the status of eideticker/b2g, could we measure the framerate
> > on this?
>
> [ I'll jump in here, since I'm the main contact for B2G/Eideticker now; mdas
> may have more information ]
>
> We have eideticker "working", minus some flakiness and bugs in the support
> for handling gestures (which may be fixed by bug 801578).
>
> The key for being able to measure something like this through eideticker
> would be being able to reproduce the test case in question. To that end, I
> guess my questions would be:
>
> 1. What is this card view?
A set of small screenshots of all running apps. The screenshots can be horizontally scrolled and when clicked on, that app opens.
> 2. Is there a way to get to the screen with this card view programatically?
> (e.g. through marionette)
Long-press on home does it. Not sure how that works in marionette.
> 3. What gesture/action do we need to produce in order to reproduce the
> performance issue? (if there is one)
If you turn on paint flashing [1], you can see that horizontal scrolling causes many flashes on the screenshots.
Jeff Muizelaar told me that the title of this bug is correct: we should use a transform instead of scrollLeft.
[1]
Settings > Device Information > More Information > Developer > Flash repainted area
Comment 14•13 years ago
|
||
> > 2. Is there a way to get to the screen with this card view programatically?
> > (e.g. through marionette)
>
> Long-press on home does it. Not sure how that works in marionette.
It looks like the way to do this programatically is to dispatch a 'holdhome' event to the window containing the system app, see:
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/cards_view.js#L571
I can help with the Marionette commands needed to do this.
Comment 15•13 years ago
|
||
(In reply to Jonathan Griffin (:jgriffin) from comment #14)
> > > 2. Is there a way to get to the screen with this card view programatically?
> > > (e.g. through marionette)
> >
> > Long-press on home does it. Not sure how that works in marionette.
>
> It looks like the way to do this programatically is to dispatch a 'holdhome'
> event to the window containing the system app, see:
>
> https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/cards_view.
> js#L571
>
> I can help with the Marionette commands needed to do this.
This turns out to be quite easy. Once you have started a marionette session, you can invoke the cards view using:
marionette.execute_script("window.dispatchEvent(new Event('holdhome'));")
If you've switched into an app frame (most of which run OOP), you'll first need to switch back to the main frame using:
marionette.switch_to_frame()
Comment 16•13 years ago
|
||
Thanks Jonathan - Will can we measure the frame rate here now?
Comment 17•13 years ago
|
||
(In reply to JP Rosevear [:jpr] from comment #16)
> Thanks Jonathan - Will can we measure the frame rate here now?
I'm having trouble reproducing the swipe gesture required to test this with the dummy input driver on the panda. I was trying to track down the underlying cause last week, and I think I may have finally figured it out:
https://bugzilla.mozilla.org/show_bug.cgi?id=783023#c19
Hopefully we can get this sorted out this week.
Depends on: 783023
Comment 18•13 years ago
|
||
Erg, my comment wasn't submitted X days ago. Removing f? since wlach is handling eideticker work.
Flags: needinfo?(mdas)
Comment 19•13 years ago
|
||
(In reply to William Lachance (:wlach) from comment #17)
> (In reply to JP Rosevear [:jpr] from comment #16)
> > Thanks Jonathan - Will can we measure the frame rate here now?
>
> I'm having trouble reproducing the swipe gesture required to test this with
> the dummy input driver on the panda. I was trying to track down the
> underlying cause last week, and I think I may have finally figured it out:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=783023#c19
>
> Hopefully we can get this sorted out this week.
Gestures are working now, but I need to add support for a new type of eideticker test to support what we're trying to do here. Working on that now.
Comment 20•13 years ago
|
||
(In reply to William Lachance (:wlach) from comment #19)
> (In reply to William Lachance (:wlach) from comment #17)
> > (In reply to JP Rosevear [:jpr] from comment #16)
> > > Thanks Jonathan - Will can we measure the frame rate here now?
> >
> > I'm having trouble reproducing the swipe gesture required to test this with
> > the dummy input driver on the panda. I was trying to track down the
> > underlying cause last week, and I think I may have finally figured it out:
> >
> > https://bugzilla.mozilla.org/show_bug.cgi?id=783023#c19
> >
> > Hopefully we can get this sorted out this week.
>
> Gestures are working now, but I need to add support for a new type of
> eideticker test to support what we're trying to do here. Working on that now.
Added bug 809730 to track this. No final patch yet, but I've gotten quite far with the idea. Should have something to show for it next week.
Depends on: 809730
Updated•13 years ago
|
Component: Gaia → Gaia::System
Comment 21•13 years ago
|
||
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "known P2 bugs found before or during C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
Updated•13 years ago
|
Assignee: timdream+bugs → dale
Updated•13 years ago
|
Assignee: dale → mbudzynski
Comment 22•13 years ago
|
||
(In reply to William Lachance (:wlach) from comment #20)
> > Gestures are working now, but I need to add support for a new type of
> > eideticker test to support what we're trying to do here. Working on that now.
>
> Added bug 809730 to track this. No final patch yet, but I've gotten quite
> far with the idea. Should have something to show for it next week.
Actually, I guess the important thing here is really the test, not the thing that we need to write the test. Created a bug to track that, and removing 809730 from the list (it's done anyway).
Comment 23•13 years ago
|
||
No idea why my last comment reset all that stuff, I thought bugzilla was designed to prevent you from doing that. Anyway, unclobbering.
Assignee: timdream+bugs → mbudzynski
Component: Gaia → Gaia::System
Target Milestone: --- → B2G C2 (20nov-10dec)
Comment 24•13 years ago
|
||
Attachment #683989 -
Flags: review?(timdream+bugs)
Comment 25•13 years ago
|
||
(In reply to Michal Budzynski (:michalbe) from comment #24)
> Created attachment 683989 [details]
> patch
This patch looks good to me. I read through it without testing it. I can give you a r+ in a moment.
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #10)
> Panning in the Cards View looks OK here at the moment (on the Otoro). Can
> you give exact STR or some way to measure the performance against a concrete
> target?
The only problem is that this patch is a little bit too big. I afraid that the work might trigger some unforeseen regression.
Actually, I seriously doubt why we are blocking release on this bug -- cards view looks OK on device, and Josh said we really shouldn't drop common features and spend time on polishing advanced features like what we are doing right now.
I prefer this gets an blocking- and have someone a+ it for landing.
blocking-basecamp: + → ?
Updated•13 years ago
|
Attachment #683989 -
Flags: review?(timdream+bugs) → review+
Comment 26•13 years ago
|
||
Should we block on this as we don't know if we will keep cardview
Flags: needinfo?(jcarpenter)
Comment 27•13 years ago
|
||
Do not block. As per Tim, resources are better spent elsewhere right now.
Flags: needinfo?(jcarpenter)
Updated•13 years ago
|
blocking-basecamp: ? → -
Comment 28•13 years ago
|
||
Comment on attachment 683989 [details]
patch
Vivien, do you think this is safe to land?
Attachment #683989 -
Flags: approval-gaia-master?(21)
Comment 29•13 years ago
|
||
Comment on attachment 683989 [details]
patch
If this is not a blocker or is not too noticeable I would said it does not make sense to take risk for it.
Attachment #683989 -
Flags: approval-gaia-master?(21) → approval-gaia-master-
Updated•13 years ago
|
Priority: P2 → --
Summary: [Cards View] Should use transform instead of scrollLeft → [Task Manager] Should use transform instead of scrollLeft
Whiteboard: [label:perf][label:system/card_view][LOE:M] → UX-P5
Comment 30•13 years ago
|
||
As this is no longer blocking-basecamp should it be moved out of the C2 milestone?
Updated•13 years ago
|
Target Milestone: B2G C2 (20nov-10dec) → ---
Comment 31•13 years ago
|
||
should we land this now ?
(after a mandatory rebase of course :) )
That's what the master branch is for :).
This would also allow us to animate the transitions with CSS, which would get higher frame rate and avoid problems like bug 836664 comment 15.
Task switcher UX has come a long way in the last week, but we still need this for buttery smooth operation.
blocking-b2g: --- → leo?
Updated•12 years ago
|
blocking-b2g: leo? → -
tracking-b2g18:
--- → +
Updated•12 years ago
|
Assignee: mbudzynski → nobody
Comment 35•12 years ago
|
||
Michal, or Cristian, is this obsolete with the new task switcher ? (I think so)
Comment 36•12 years ago
|
||
yes it is obsolete IMHO
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•