Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature]: Allow launching in incognito mode
See original GitHub issueCurrently, puppeteer.launch opens a non-incognito context, and while one can open an incognito context via createIncognitoBrowserContext, this seems like an unnecessary hassle, especially since an extra context was created (and remains open).
Chromium supports launching in incognito mode via -incognito, but specifying this in puppeteer.launch let’s Puppeteer still think that it’s a non-incognito context: isIncognito returns false, which may cause some problems.
It would be nice to have a documented way of doing this, via a boolean option in puppeter.launch.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@OrKoN Don’t you mean “assumes that the default browser context is *non-*incognito” ?
I think it’s actually a bug in Puppeteer which assumes that the default browser context is non-incognito. It should probably derive it from the actual running browser context. The entire
isIncognitocheck in Puppeteer does not look very robust.