Closed
Bug 931968
(Frame-Rate-Drop-DOM)
Opened 11 years ago
Closed 7 years ago
Frame Rate Drop Root Cause: DOM
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 would like to be able to identify what DOM is associated with a drop in frame rates. Acceptance Criteria: * find in the recording places where frame rates drop * Be able to see what type of graphical computing is going on: for example painting, rendering, reflows, etc... * Bel able to see the DOM element associated with the graphical computing that takes a long time. * Be able to distinguish from external slow down causes versus problems my own app is causing. In other words the recording should be tab specific or app specific (FxOS). Note: sister user story to 931959: Frame-Rate-Drop-JS. there are several scenarios that JS can cause slowdowns, we may want to break up this user story into the scenarios. For example: * TIme spent in JS engine is short, but subsequent graphics consumption is high * Time spent in JS engine is long, not necessarily associated with high graphics consumption. Visualization could be done via time-based flame chart where every frame is broken down into where the browser spends time.
As a web app developer, I would like to be able to identify what DOM is associated with a drop in frame rates. Acceptance Criteria: * find in the recording places where frame rates drop * Be able to see what type of graphical computing is going on: for example painting, rendering, reflows, etc... * Bel able to see the DOM element associated with the graphical computing that takes a long time. * Be able to distinguish from external slow down causes versus problems my own app is causing. In other words the recording should be tab specific or app specific (FxOS). Note: sister user story to 931959: Frame-Rate-Drop-JS. there are several scenarios that JS can cause slowdowns, we may want to break up this user story into the scenarios. For example: * TIme spent in JS engine is short, but subsequent graphics consumption is high * Time spent in JS engine is long, not necessarily associated with high graphics consumption. Visualization could be done via time-based flame chart where every frame is broken down into where the browser spends time.
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)
Component: Developer Tools: User Stories → Developer Tools: Performance Tools (Profiler/Timeline)
Comment 1•7 years ago
|
||
I believe these user stories are no longer relevant.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•