w3c/event-timing Issues

Last updated May 18, 2024, 5:53:31 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

9 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#15	Remove modifications to other specifications	❌	5.5 years	5.4 years
#51	Provide more explanatory material in processing model	❌	5 years	5 years
#92	Address accessibility issues	❌	3.8 years	3.7 years
#114	Move some definition of interactionID to UI Events	❌	2.4 years	2.3 years
#123	Spec should clarify value of `renderingTimestamp` whenever there is no next rendering opportunity.	❌	1.6 years	1.6 years
#129	Consider measuring Events until alternative end points (i.e. visibility change, page unload, URL update for same-document navigations, fullscreen)	❌	1.4 years	1.4 years
#131	Consider exposing renderTime to Event Timing	❌	1.3 years	1.3 years
#134	Expose interactionId to keypress	❌	11.4 months	11.1 months
#137	Broken references in Event Timing API	❌	3.8 months	3.5 months