Closed rviscomi closed 2 years ago
After some investigation, I don't think this bug was caused by the INP changes, but they do make the bug more easily reproducible.
You can also reproduce this using the production version of the extension. Instead of triggering INP after the page visibility change, try to trigger CLS. For example, go to https://www.nytimes.com/ and scroll down the entire page after the visibility change. There should be an increase to CLS, and LCP will be reset to 0.
Initial state:
After a visibility change and scrolling:
The expected behavior is for metrics to persist their values across visibility changes.
Steps to reproduce:
HUD after Step 1 and Step 3:
HUD after Step 4: