Closed Bug 894939 Opened 7 years ago Closed 6 years ago
Improve Browser panning and content repainting performance
User Story: As a user when I am surfing the web, the Firefox OS browser should feel responsive/snappy and re-paint the screen consistently at 55-60 fps when I pan around a web page. Benchmark stats to define "responsive/snappy" from the user dragging the content to panning: *50ms lag when panning for visual feedback Acceptance criteria: *User can consistently pan around web content with a drag to pan lag time of <=50ms *The browser content repaints at >=55fps
Just noted in bug 894954, we need to find a way of automating the testing of this. I think investigation into this can be considered as sprint ready now.
Whiteboard: [c= p= u= s=] → [c= p= u= s=],[sprintready]
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/55559964
Karen Rudnitski deleted the linked story in Pivotal Tracker
Brad, Is the Browser taking this one or looking for fxos-perf to pick it up? Mike
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
(In reply to Mike Lee [:mlee] from comment #4) > Brad, > > Is the Browser taking this one or looking for fxos-perf to pick it up? > > Mike We're hoping that the work to enable the tiled layer backend will help here, but it'd be great for someone to look at effectively measuring these numbers.
As Chis said, our tiles work is intending to improve panning perf.
Now that APZC and tiling have landed, is this still a valid bug?
Yes, but perhaps it's better tracked by specific bugs now. Panning performance is pretty good on the whole atm, I don't think this bug helps us.
From comment 8, closing this bug for now. Please reopen specific browser bugs if this is an issue.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Whiteboard: [c= p= u= s=],[sprintready] → [c=handeye p= u=2014.05.23 s=],[sprintready]
Whiteboard: [c=handeye p= u=2014.05.23 s=],[sprintready] → [c=handeye p= s=2014.05.23.t u=] [sprintready]
You need to log in before you can comment on or make changes to this bug.