First Input Event Timing data sometimes missing |
|||
Issue descriptionRepro: 1. Dispatch a mouse move event which takes > 50ms. 2. Dispatch a click event. I expect to see an event timing entry for the mousemove, and then a first event entry for the click. The first event entry is missing.
,
Oct 23
This is with a PO registered immediately. I suspect that the code to prevent us from firing first-input multiple times is broken.
,
Oct 23
Please provide a sample testcase. I tried the following and it works as expected: <!DOCTYPE HTML> <meta charset=utf-8> <title>Mousemove then click</title> <body> <p><a href="http://developer.mozilla.org/" id="mousy">Move your mouse here…</a></p> <div id="bla" onclick="performance.now();">ClickME</div> <script> const observer = new PerformanceObserver( function(entryList) { entryList.getEntries().forEach(entry => { console.log(entry.entryType); }); }); observer.observe({entryTypes: ['firstInput', 'event']}); document.getElementById("mousy").onmousemove = () => { let p = performance.now(); while(performance.now() < p + 100) {} } </script> </body>
,
Oct 24
Discussed with Tim in person, it seems this is working as intended. The explainer may need to be updated to allow not producing first input events when there are no event handlers. |
|||
►
Sign in to add a comment |
|||
Comment 1 by npm@chromium.org
, Oct 22