Closed Bug 1163901 Opened 9 years ago Closed 2 years ago

Integrate frame-timing API to timeline

Categories

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

Product:
DevTools
Component:
Performance Tools (Profiler/Timeline)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: paul, Unassigned)

References

Details

(Whiteboard: [devtools-platform])

We need to investigate how the new Frame Timing API can help us. I haven't looked property at the API, but it looks like it could be useful. Scanning quickly thought the spec, I think it can help us: - record FPS - record duration of a tick - record async animations (not part of the main-thread tick) - record async scroll timing - record composite operations This might deeply impact the way our markers work. We want to understand what *new* timing data are available. We want to understand what *existing* markers can be inferred from this new API (implying that we want to re-implement how these markers are recorded). We want to understand what markers can't be re-implemented with this new API, and maybe suggest to extend the API.
See "Intent to implement: Frame Timing API" dev-platform thread.
Depends on: 1158032
Whiteboard: [devtools-platform]
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
Priority: -- → P3
Version: 26 Branch → unspecified
Product: Firefox → DevTools

Frame timing spec has been abandoned. Closing this as WONTFIX.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.