Nicolás Peña Moreno

It seems feasible but also somewhat costly because there are certain computations that are only done in Element Timing (LCP does not expose the rects), and we'd need to create...

Slowest X before user input could work, I guess. But not clear why you want slowest instead of largest, or some other criteria?

This seems reasonable to me, although it would be great to hear from some Element Timing API users (or potential users) that this would be useful to them.

I agree we should reconsider this since some sites rely on canvas to produce their main content.

No, sorry :( @MatRivard do you have some use-cases you could share? I think having concrete developers and sites interested in using this will help prioritize it more.

SVG is pretty complex so I filed https://github.com/WICG/element-timing/issues/56 to track that separately!

I don't understand why the current threshold is insufficient. Is it because you're profiling a very small percentage of users and hence not getting enough data samples? You can solve...

In Element Timing, we do not expose the render time of the image if the TAO checks don't pass. That said, you can already obtain image decoding times via `decode()`,...

Looking at tests, looks like modifying transform should not result in an entry (https://github.com/web-platform-tests/wpt/blob/master/layout-instability/transform-change.html), but transform needs to be considered when computing viewport overlap (https://github.com/web-platform-tests/wpt/blob/master/layout-instability/transform.html).

If the site is performing animations or such, longtasks would still present unoptimal experiences to the user, no? One idea is to expose whether isInputPending was called during the longtask,...