Support running sessions with --incognito flag

[christian-bromann]

It seems like WebDriver Bidi is failing to run the session when an --incognito flag is set. When adding the flag I get 2 browser windows (instead of usually 1 window with 2 tabs) where the Bidi is actually running incognito while the actual session isn't:

Expected Behavior:

Have both browser windows open incognito.

[OrKoN]

--incognito flag is generally flaky for automation and not well supported. We recommend using https://w3c.github.io/webdriver-bidi/#command-browser-createUserContext to create an isolated context.

[christian-bromann]

Is creating a new user context identical to running in incognito? Or are there specific browser settings that come when using incognito. I am especially wondering about this user comment:

but the prompts from chrome password manager, retained cache and similar are still causing a lot of troubles. Certain reported bugs in our system i was able to reproduce in incognito browser yet automation running same steps failed. Incognito is precious and i have not experienced any issues while in incognito before upgrade.

I was under the assumption that running a WebDriver session is essentially like running incognito but appears that some browser features behave differently.

[OrKoN]

Is creating a new user context identical to running in incognito?

yes, in Chrome it is an off-the-record profile similar to incognito but you can have multiple. Each user context is isolated in terms of storage/cookies/caches.

I was under the assumption that running a WebDriver session is essentially like running incognito but appears that some browser features behave differently.

that is controlled by the --user-data-dir and whether it is empty or not. Other feature flags might be used to turn off Chrome features. I do not expect the password manager or caches to work in a fresh user context.