[Responsiveness Metrics] - Select Elements

[Dave Smart]

Hi All,

Been having a play with the JavaScript Demos on https://web.dev/responsiveness/ & Hongbo Song's excellent article here: https://calendar.perfplanet.com/2021/hands-on-with-the-new-responsiveness-metrics/

This is perhaps me missing the point, but both show high latency for select elements on desktop, with a plain html select element recording latency of ~2-3 seconds (testing in chrome canary)

Web.dev example: https://testing.tamethebots.com/selecttest.html
perfplanet example: https://testing.tamethebots.com/selecttest-2.html

This doesn't occur in canary chrome on Android, which just records the click event, so I presume it's down to the human delay between pointer down and selecting an option? (If you use the keyboard to tab to the select and the arrow / enter keys, there's no issues).

Is this as intended? Is there some way we can account for this?

[Nicolás Peña Moreno]

It is not intended for native select elements to have very long latencies. However I tried to reproduce this but couldn't. I think you are just clicking on the select elements and choosing options, right? Do you find consistent latencies of 2-3 seconds? Perhaps a screenshot of the console output would help. Also, which Chrome version are you using, and which OS?

--
You received this message because you are subscribed to the Google Groups "web-vitals-feedback" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web-vitals-feed...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/web-vitals-feedback/b5bbbfbb-22bd-4abc-a5d1-ca718dfb2dc2n%40googlegroups.com.

[Dave Smart]

Hi, 

Not consistently 2-3 it seems, but consistently large:

That's chrome 99.0.4777.0 on Windows 10.

[Nicolás Peña Moreno]

Thanks, it seems like a Windows problem. From a quick glance it looks like the issue are the event timestamps surfaced. The code snippets could be updated to ignore bogus (0 or negative) event timestamps, but I've also filed https://bugs.chromium.org/p/chromium/issues/detail?id=1281701 since we want this to work properly. Thanks for noting this problem!

To view this discussion on the web visit https://groups.google.com/d/msgid/web-vitals-feedback/91cdbb29-cc59-405a-bbf9-3353f6c56561n%40googlegroups.com.

[Dave Smart]

Thanks for the info, and opening the bug report!

[Dave Smart]

Brilliant to see this metric rolling out to CrUX.

This particular issue still seems to be present on windows, (tried in Canary chrome) 

Is this just an issue in the JavaScript API or does it affect data sent to CrUX too?

[Philip Walton]

Thanks for pinging this thread, Dave.

I believe this issue just affects the JS API and not the data you see in CrUX. But the JS API is obviously very important as well, so we're going to prioritize getting this fixed.

To view this discussion on the web visit https://groups.google.com/d/msgid/web-vitals-feedback/aedf8bd2-66cc-40fa-bbd7-879f76a1dc0an%40googlegroups.com.

[Dave Smart]

Thanks for the info, Philip!