You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open question on whether to / how best to support as this is moving away from a "page load" metric to something more journey based. Wonder whether worth exploring decoupling "record" and "stop" so users can inject their own Cypress driven journey in the middle (pertinent clicks, hovers, etc.), though this would result in losing the current "batteries included" approach of one command "doing it all".
Being able to record the click through journey will definitely be value-able.
Often analytics such as adobe analytics will show an issue and the only way to recreate is through a series of clicks to trigger that bad state at a specified viewport.
Issue
Details
Placeholder to consider support for the new Interaction to New Paint (INP) web vital. See https://web.dev/inp/.
At the time of writing there are a couple of open bugs on the web-vitals package repo, so may be premature to add as "stable" atm. See:
Open question on whether to / how best to support as this is moving away from a "page load" metric to something more journey based. Wonder whether worth exploring decoupling "record" and "stop" so users can inject their own Cypress driven journey in the middle (pertinent clicks, hovers, etc.), though this would result in losing the current "batteries included" approach of one command "doing it all".
Some notes on implementation detail: https://web.dev/inp/#measure-inp-in-javascript
The text was updated successfully, but these errors were encountered: