Support for "networkidle2"

[rjyo]

Most SPAs will use async data and currently rendora only supports waitAfterDOMLoad: milliseconds.

Wait a fixed time is not good enough at most times. Is it possible to add an option like puppeteer's

await page.goto('https://news.ycombinator.com', {waitUntil: 'networkidle2'});

[geokb]

I think I might do that if there is enough interest, the problem is that networkidle2 isn't really based on anything in the chrome-devtools-protocol itself, it's just a heuristic made by puppeteer, and they still impose a safeguard interval of 500ms after the last 2 requests as far as I am aware for the case of networkidle2. On the other hand, setting a "large enough" value of waitAfterDOMLoad according to your application does the same thing in the end. Anyway I'll have a look at the implementation of puppeteer and try to use it here. Probably I'll have to add waitUntil under the headless configuration namespace that will override waitAfterDOMLoad

[kapouer]

You could inject a script that hooks into:

• setTimeout if it has a small value
• xhr, fetch
• <script>
• promise
• raf
• window, document loading events

to determine when page has done all interesting things.
I'm doing that right there but it's really specific to this engine.

[wpajqz]

I think it's ok
wpajqz@15adfdf