Search results

PerformanceEntry.id is shadowed by PerformanceElementTiming.id.

Status: Open.

#218 In w3c/performance-timeline;

· powdercloud opened on Mar 18, 2025

Consider changing the spec text to allow <code>buffered</code> with <code>entryTypes</code>

Status: Open.

#215 In w3c/performance-timeline;

· hiikezoe opened on Jan 8, 2025

<code>droppedEntriesCount</code> can be inconsistent with reported entries

Status: Open.

#214 In w3c/performance-timeline;

· rubennorte opened on Sep 23, 2024

<code>PerformanceObserver.supportedEntryTypes</code>can't be annotated with <code>[SameObject]</code>

Status: Open.

#212 In w3c/performance-timeline;

· petervanderbeken opened on Apr 18, 2024

Cross-origin timeline support

Status: Open.

#207 In w3c/performance-timeline;

· clelland opened on Feb 7, 2023

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

Status: Open.

#206 In w3c/performance-timeline;

· noamr opened on Feb 5, 2023

Consider renaming PerformanceObserverCallbackOptions

Status: Open.

#199 In w3c/performance-timeline;

· kenchris opened on Mar 16, 2022

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

Status: Open.

#182 In w3c/performance-timeline;

· nicjansma opened on Jun 24, 2021

Hard to feature-detect observe() parameters

external-dependency

Status: Open.

#176 In w3c/performance-timeline;

· npm1 opened on Sep 22, 2020

Fire Paint Timing events for soft navigations

SPA-reporting

Status: Open.

#168 In w3c/performance-timeline;

· dwsmart opened on Jun 17, 2020

PerformanceEntries are affected by backgrounded status

Status: Open.

#105 In w3c/performance-timeline;

· npm1 opened on Jul 25, 2018

· 

Level 3

When a UA is under memory pressure, what the proper way to shrink buffers in timeline?

Status: Open.

#101 In w3c/performance-timeline;

· toddreifsteck opened on Feb 22, 2018

· 

Level 3