Nicolás Peña Moreno

**Which events**: https://wicg.github.io/event-timing/#sec-events-exposed. Note that we expose first-input (where the types are a subset of those) always, and slow events. **How are they dispatched**: I don't understand this question. "They"...

That information can be obtained via event.composed, no? There's no need to patch all the places. When event.composed is false and the target is in the shadow DOM, we cannot...

They are dispatched from the DOM event dispatch algorithm, so again, that's the only thing that needs to change. What would I need to change from, for example, https://w3c.github.io/uievents/#event-type-mousedown?

I guess the question is whether it will ever be possible to remove the 'obsolete' APIs right? I think last time we checked, the usage was extremely high and hence...

Interesting observation! I think that we could change user timing to use PerformanceNavigationTiming instead of PerformanceTiming. It looks like the names used in one or the other are almost the...

Just to clarify, sounds like this applies to https://w3c.github.io/hr-time/#dfn-time-origin as well? If it does then this would be a pretty big change impacting any high resolution timestamps received by developers.

Oh hi Todd :) I think the diagram is supposed to imply that, but it should probably be made clearer by moving `workerStart` up to be next to `fetchStart`

@nicjansma did you accidentally remove the PR preview link from the first comment? I was hoping to look at the new diagram since I just realized I commented on the...

Yea, this makes sense, I think this is what they're calling `workerReady` in https://github.com/w3c/resource-timing/issues/119. Are you thinking on adding a new parameter in this PR though? Or just updating the...

Let us know when you'd like another review on this