931968 - (Frame-Rate-Drop-DOM) Frame Rate Drop Root Cause: DOM

Status: RESOLVED WONTFIX

(DevTools :: Performance Tools (Profiler/Timeline), defect)

Description

[Axel Kratel]

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.

Comment 1

[Greg Tatum [:gregtatum]]

I believe these user stories are no longer relevant.