Nicolás Peña Moreno

Ok, let's validate the cost question within Chrome and then come back to this with a decision.

We currently do not plan to expose the script URL, AFAIK. We don't have any concrete future work on how to make attribution better in general. This was deprioritized because...

Yes, right now there is no buffered flag behavior nor performance timeline buffering for longtask entries, so they would only need to be kept alive if a PerformanceObserver looking at...

Yes, although for different resource types. Consolidating still seems reasonable to me.

Similar issue: https://github.com/WICG/element-timing/issues/64

One problem though is that for the third use case this is not great because WPT.fyi uses Chrome dev so it will not immediately reflect bug fixes.

I don't know what's special but the results do behave somewhat differently in some cases. A simple example of a difference is that the viewport size is different in Chrome...

Re last question, I'd be mostly interested in ToT which gives the most 'up to date' results, but I guess Dev is close enough.

> I agree with you that some of the ChromeStatus fields are not always relevant for every change. This includes, but is not limited to, WebDriver changes. Not limited to...

Correct! I mention that we might not be able to provide this at first because on our text [proposal](https://docs.google.com/document/d/1xhPJnXf0Nqsi8cBFrlzBuHavirOVZBd8TqdD_OyrDGw/edit?usp=sharing) we do not wait until webfonts have loaded. In the future,...