Issues · w3c/performance-timeline · GitHub

Labels Milestones

Add PerformanceObserver option for "per-paint" reporting.

#228

· mmocny opened

on Mar 26, 2026

PerformanceEntry.id is shadowed by PerformanceElementTiming.id.

#218

· powdercloud opened

on Mar 18, 2025

Consider changing the spec text to allow `buffered` with `entryTypes`

#215

· hiikezoe opened

on Jan 8, 2025

`droppedEntriesCount` can be inconsistent with reported entries

#214

· rubennorte opened

on Sep 23, 2024

`PerformanceObserver.supportedEntryTypes`can't be annotated with `[SameObject]`

#212

· petervanderbeken opened

on Apr 18, 2024

Cross-origin timeline support

#207

· clelland opened

on Feb 7, 2023

Proposal: clock-drift correction, potentially with opt-in

#206

· noamr opened

on Feb 5, 2023

Consider renaming PerformanceObserverCallbackOptions

#199

· kenchris opened

on Mar 16, 2022

API shape for monitoring new navigation-like entries such as App History, BFCache, etc

#182

· nicjansma opened

on Jun 24, 2021

Hard to feature-detect observe() parameters

external-dependency

#176

· npm1 opened

on Sep 22, 2020

Fire Paint Timing events for soft navigations

#168

· dwsmart opened

on Jun 17, 2020

PerformanceEntries are affected by backgrounded status

#105

· npm1 opened

on Jul 25, 2018

·