Closed
Bug 932008
(Find-frequ-Rredraws)
Opened 11 years ago
Closed 7 years ago
Find Frequent Redraws in a Recording
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: akratel, Unassigned)
References
Details
(Whiteboard: [User Story], [mockup])
User Story
As a web App developer, I'd like to easily find frequent redraws within a recording and be able to drill down to the DOM objects and/or JS that are related to the frequent redraws so that I can optimize my CSS and/or JS related to the redraw and potentially eliminate it. Note: we currently have a way to graphically show the frequent redraws via the highlighter, but the highlighter doesn't necessarily show which DOM element is involved, nor does it easily show the JS. It would be easier to do this for example via a flame chart that can be filtered for events that are redraws and sorted in order of most # of events to least number of events. Related User Story: 931968: "Frame Rate Drop Root Cause: DOM" which also requires the ability to map back to the DOM. for example, via such a sortable flame chart, we could show that one particular DOM node caused 220 paint events during the last minute.
As a web App developer, I'd like to easily find frequent redraws within a recording and be able to drill down to the DOM objects and/or JS that are related to the frequent redraws so that I can optimize my CSS and/or JS related to the redraw and potentially eliminate it.
Note: we currently have a way to graphically show the frequent redraws via the highlighter, but the highlighter doesn't necessarily show which DOM element is involved, nor does it easily show the JS. It would be easier to do this for example via a flame chart that can be filtered for events that are redraws and sorted in order of most # of events to least number of events.
Related User Story: 931968: "Frame Rate Drop Root Cause: DOM" which also requires the ability to map back to the DOM.
for example, via such a sortable flame chart, we could show that one particular DOM node caused 220 paint events during the last minute.
Reporter | ||
Updated•11 years ago
|
Flags: pm-scrub?
Reporter | ||
Updated•11 years ago
|
Component: Developer Tools → Developer Tools: User Stories
Reporter | ||
Updated•11 years ago
|
User Story: (updated)
Comment 1•10 years ago
|
||
I think the new performance tools get close to this, but maybe lack the ability to map directly to the offending DOM element(s) -- like highlighting the corresponding DOM element when selecting a specific marker, for example? What's remaining here?
Component: Developer Tools: User Stories → Developer Tools: Performance Tools (Profiler/Timeline)
Comment 2•7 years ago
|
||
I believe this is no longer relevant for current planned work.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•