Closed chaosharmonic closed 1 month ago
So on some further tinkering it looks to stem from page.goto
and its default behavior of using networkidle2
as a waitFor
option.
Setting waitFor
to load
or networkidle0
appears to resolve the issue, but I'm also not clear enough on how page.waitForNetworkIdle
and its idle connection listening is supposed to work to be sure how much this is a bug or intended behavior that I should be passing in an override option for.
Closing this for now as I'm not actually sure it was a bug. On digging further (a while ago) I'm pretty sure this is that the Celestial network bindings weren't actually wired up until an update pushed shortly before I opened this issue.
Opening a new page will occasionally throw errors, with the below output, despite the pages themselves successfully loading. Affected sites include LinkedIn, Indeed, and Glassdoor, and it appears to in some way relate to persistent network requests (to tracking APIs, for instance) on page load.
This started after I switched to the version on JSR, and looks to be from a call to
Celestial.network.enable({})
inbrowser.ts
, introduced inc13b687
, just after the last version on/x/
. I haven't isolated why, but when I comment this out, it stops happening.