event-timing/pull/160 *Specification* https://github.com/w3c/event-timing/pull/160 *Summary* The Event Timing API is part of the Performance Timeline and is used to measure

Contact emails nrosenthal@chromium.org, shaseley@chromium.org Explainer https://github.com/w3c/long-animation-frames/blob/main/user-defined-script-

animation-frame/tentative/loaf-source-location-redirect.html?label=experimental&label=master&aligned >> . Do they represent anything worth worrying

. > > * WPT tests > > Very comprehensive: > https://wpt.fyi/results/long-animation-frame/tentative?label=experimental&label=master&aligned >

event-timing/INP. > > > Security > > This feature exposes rendering time to iframes, which might be > cross-origin (same-process). However, this is anyway observable

) the frame has been rendered (could be more than one task) 2) the task is complete and there are no changes (a classic long task without visual updates). - Add information about how long

. The frame timing API will help, but it >>>> won't be enough to correlate directly with input. >>>> >>>> Simply plumbing through a useful

Contact emails mpb@chromium.org, igrigorik@chromium.org, nduca@chromium.org Spec http://w3c.github.io

I didn't send these for the past two weeks due to the holiday. Date Sender Intent to Description

w3c/frame-timing/wiki/Explainer: > "Because of these subtleties, the browser will never have enough > information about your app to make intelligent decisions as

in new frame with the same contents as the previous frame). Let me go through the possible scenarios and explain how this would work. A) Flush request received when there is nothing pending