Closed
Bug 928447
Opened 11 years ago
Closed 6 years ago
Add a simple UI in the system app that displays the number of reflows.
Categories
(Firefox OS Graveyard :: General, defect, P2)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: vingtetun, Assigned: vingtetun)
References
Details
(Keywords: perf, Whiteboard: [c=devtools p= s= u=])
Because reflows are not cool, let's add a simple box next to the fps counter or the load time stuff to display the number of reflows. The initial idea I have about that is to have 3 boxes: - One for the system app - One for the keyboard when it is opened (this one can leave at the bottom of the screen) - One for the current app. Then the number of reflos will just be incremented every time. In order to reset them the developer needs to click on one of the box, then all of them are resetted. A setting to turn that on/off in the Developer section of the settings app would be nice. It may not be the perfect UX but at least it is practical.
Assignee | ||
Comment 1•11 years ago
|
||
fwiw the current plan is to build that on top of the devtools built in bug 926371 to get informations. Then those will be sent to the system app thought a mozChromeEvent or similar. So the UI will be in Gaia.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → 21
Comment 2•11 years ago
|
||
There's also bug 926922 coming that will capture more information about reflow/style flushes in profiles. But I support adding ways to make it easier to see at a glance when users are not profiling!
See Also: → 926922
Comment 3•11 years ago
|
||
Would it also be possible to add some information to count how much time has spent during reflow as well? It would be awesome to know how much reflow costs. So maybe uplift the devtools.webconsole.filter.csslog data as a developer preference?
Priority: -- → P2
Whiteboard: [c=profiling p= s= u=] → [c=devtools p= s= u=]
Comment 4•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•