react-scan
react-scan copied to clipboard
Bug: infrequent reporting of large interaction times
Notifications sometimes reports large interaction times, when there was no large interaction in reality.
This is probably an interaction that got matched with the wrong performance event due to overlap/async reporting. This can probably be fixed by no longer using the performance event API for compositing/GPU times (which we currently do not show anywhere in the UI other than the prompt section)