Timothy C. Quinn

An alternative to this PR would be to change the code to always wait for browser to close. I have not done testing but I suspect that this may not...

Question: Shouldn't `waitForChromeToClose()` be made `async`?

Here is my test page for this new functionality: ````html Test Page function MyOBJ(){ this.foo = "foov" this.bar = "barv" } console.log(".: INT :.") console.log(1) console.log(".: NULL :.") console.log(null) console.log(".:...

FYI - I just got burned by the 'Binding 'a' failed' issue. It caused the launched terminator window to be bound to the launching windows process rather than being independent....

You are correct, the the screenshot API is not implemented in the [Page.captureScreenshot Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-captureScreenshot). I've updated my comment above to reflect this.

The recursive setting does exactly what I need. I'll look into the templates as you suggest. Thanks for the great tool set!

I have confirmed that this issue can be resolved by adding the following code to the examples. ``` process.on('SIGTERM', function () { console.log('Got SIGTERM, exiting...'); nc.cleanup(); win.close(); process.exit(0); }); process.on('SIGINT',...

There has been activity with google on this lately: - https://github.com/GoogleChromeLabs/chromium-bidi/issues/518 - https://bugs.chromium.org/p/chromedriver/issues/detail?id=3517 - https://bugs.chromium.org/p/chromedriver/issues/detail?id=4070

That is massive. Did you try doing it by hand to see the resulting size? This does not sound like a pypeteer bug. There may be more efficient ways of...

Same question here...