w3c / event-timing

A proposal for an Event Timing specification.

https://w3c.github.io/event-timing/

w3c/event-timing Issues

Audit the list of events which Event Timing api should report (and consider adding focus/blur)
Updated 2 years ago1
Consider measuring Events until alternative end points (i.e. visibility change, page unload, URL update for same-document navigations, fullscreen)
Updated 2 years ago
Broken references in Event Timing API
Closed 2 years ago
Consider replacing `performance.interactionCounts` map-like with a `performance.interactionCount` number
Closed 2 years ago2
Consider exposing event target ID (for cases where target is detached)
Updated 2 years ago4
Default buffering of Event Timing Entries is based on durationThreshold: 104 -- even for Interactions.
Updated 2 years ago6
Spec should clarify value of `renderingTimestamp` whenever there is no next rendering opportunity.
Updated 2 years ago
How does Event Timing API relate to/overlap with Long Tasks API?
Updated 2 years ago
"has dispatched input event" should only be set for trusted events
Updated 2 years ago3
Proposal: DOM event identifier which can map to EventTimingPerformance entry
Updated 2 years ago2
Update research reference to more current research
Updated 2 years ago3
CfC: Adopt Event Timing into the WebPerfWG as a Working Draft
Closed 2 years ago1
Proposal: add page visibility attribute to PerformanceEventTiming entry
Closed 3 years ago4
interactionID should be harmonized with activation triggering input events
Closed 3 years ago6
Move some definition of interactionID to UI Events
Updated 3 years ago
Expose the number of interactions to the webpage
Closed 3 years ago
Proposal: add more main thread activity information to PerformanceEventTiming entry
Updated 3 years ago2
CFC: adopt to WebPerfWG as a Working Draft
Closed 3 years ago4
An event is not its type
Closed 3 years ago
Event's delay is rather vague
Closed 3 years ago9
Clarify arbitrary constants in the spec
Closed 3 years ago2
Support for mousemove and other continuous events
Updated 3 years ago4
toJSON() shouldn't include target attribute
Closed 4 years ago2
The definition of first input is imprecise & lacking
Closed 4 years ago5
Add a note to caution about meaningfulness of first event
Closed 4 years ago
Address accessibility issues
Updated 4 years ago
Event Timing spec is up!
Closed 4 years ago3
"Queuing other entries" section is confusing
Closed 4 years ago7
It is surprising that 'wheel' event is exluded from the event timing
Updated 4 years ago1
Add a normative definition for first input delay (FID)
Closed 4 years ago1
First input should ignore events before First Contentful Paint?
Closed 4 years ago6
"nearest multiple of 8" in "dispatch pending Event Timing entries" must specify the unit
Closed 4 years ago6
Remove the mention of "RAIL performance model" in security and privacy considerations
Closed 4 years ago
Add element and/or id fields to PerformanceEventTiming to indicate target of the event
Updated 5 years ago3
Considered for event timing: drag & drop
Closed 5 years ago2
First Input Delay and first-input event type
Closed 5 years ago
Set baseline of 100ms for duration
Closed 5 years ago3
Alternate semantics for processingStart
Updated 5 years ago9
Should Section 2.2 reference 'considered for Event Timing'
Updated 5 years ago
Semantics behind list
Updated 5 years ago5
"Approximate the 75'th percentile of click event queueing times." as a use case does not make sense
Closed 5 years ago6
Provide more explanatory material in processing model
Updated 5 years ago
Various uses of public JavaScript APIs
Closed 5 years ago2
Unclear the maplike does what you're expecting
Closed 5 years ago
Formatting/style nits
Closed 5 years ago4
Set up PR preview
Closed 5 years ago
"finalize event timing" append step seems wrong
Closed 5 years ago
Use implements to check type
Closed 5 years ago1
Which events to capture? The current setup is a bit strange.
Closed 5 years ago7
"Dispatch pending entries" is too generic of a name
Closed 5 years ago