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
The problem with pagewaitforloadstatestate is that, if the page wasn't built before next.js triggers the browser redirect after the build is completed. So the actual readyState is 'complete'. This is indicated by the tiny (and lovely) triangle at the lower right corner. I could use a selector and wait for the div to disappear. But maybe it's somehow possible to wait for the corresponding events written to the console ([Fast Refresh] done).
Has somebody already invested time in this or has somebody a sweet solutions for this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there!
I use playwright-community/jest-playwright to test my next.js site. Their docs recommend using pagewaitforloadstatestate or timeouts to wait for page transitions.
The problem with
pagewaitforloadstatestate
is that, if the page wasn't built before next.js triggers the browser redirect after the build is completed. So the actual readyState is 'complete'. This is indicated by the tiny (and lovely) triangle at the lower right corner. I could use a selector and wait for the div to disappear. But maybe it's somehow possible to wait for the corresponding events written to the console ([Fast Refresh] done).Has somebody already invested time in this or has somebody a sweet solutions for this?
Beta Was this translation helpful? Give feedback.
All reactions