Timothy Dresser

It's unclear to me how excluding redirect time in the timeOrigin prevents any realistic attack. For this attack to work today, we need: - a redirector which forwards to a...

I'm hoping that the Element Timing API will, over time, be extended to handle the first two cases. When should font processing time end? If this is hung off of...

Sorry, yes, long tasks will only handle a subset of the JS case. How high priority is the sub 50ms JS case?

> Hero Image/element timing assumes there is minimal distinction between decode and in-view, but I would argue that this is an important distinction in the real-world as a validation metric...

Computing the critical path is difficult in general, though there may still be value to your proposal. An example of why computing the critical path is extremely difficult: N JS...

@n8schloss - Ilya mentioned you've had some thoughts here in the past? Are you aware of any previous discussion?

"I think it’s pretty clear what constitutes throttling, it’s whenever the browser slows down JS execution purposefully. Specific examples can be provided, like not honoring small timeout values in setTimeout,...

"If it's something large enough to affect the reliability of the RUM metrics, it should be flagged." Yeah, I think this is roughly correct, but extremely difficult to spec, and...

* I think we do need to be able to distinguish frames. The current [long tasks V2 explainer](https://docs.google.com/document/d/1iUmC6zb9jPG5Tk1jJ2vcRL1V0xSeVRM1_zR04GKMOYE/edit) mentions, but doesn't clearly define `containerType`, `containerSrc`, `containerId` and `containerName`. Firming up...

Sorry, I was wrong about the first point. These fields are defined [here](https://w3c.github.io/longtasks/#sec-TaskAttributionTiming). Adding some subset of these to PerformanceEntry would be a plausible approach.