-
Notifications
You must be signed in to change notification settings - Fork 13
Issues: w3c/event-timing
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Consider removing pointermove (and interactionType and pointerIsDragSet)
#140
opened Sep 12, 2024 by
mmocny
Audit the list of events which Event Timing api should report (and consider adding focus/blur)
#130
opened Jan 5, 2023 by
mmocny
Consider exposing event target ID (for cases where target is detached)
#126
opened Nov 29, 2022 by
mmocny
Default buffering of Event Timing Entries is based on durationThreshold: 104 -- even for Interactions.
#124
opened Oct 11, 2022 by
mmocny
Spec should clarify value of
renderingTimestamp
whenever there is no next rendering opportunity.
#123
opened Sep 30, 2022 by
mmocny
"has dispatched input event" should only be set for trusted events
#121
opened Jul 4, 2022 by
yoavweiss
Proposal: DOM event identifier which can map to EventTimingPerformance entry
#108
opened Oct 31, 2021 by
nhelfman
ProTip!
no:milestone will show everything without a milestone.