Maksim Sadym

The question is do we want to restrict the protocol extensions. And having the nested handlers can be considered as such an extension.

Is issue reproducible in `headful` mode?

Adding @vladimir-nechaev who is working on ChromeDriver Classic

> diff --git a/javascript/atoms/dom.js b/javascript/atoms/dom.js Thanks for providing the diff!

So the suggested way is attractive, but I guess we should not extend the Classic protocol with BiDi format. To avoid that, we can pass a `deserialization algorithm`, or more...

> Sure, if we don't want to just allow the new format in classic then passing in the deserialization steps is a pretty clean approach. `is element origin` and `get...

@whimboo next week, after my vacation. Or feel free to ping other our folks

I'm not sure if it's possible to implement `"extensionsInstallTemporarily": false` in Chrome. WRT `extensionsAllowPrivateBrowsing`, is it still required, if we have UserContexts?

Closing, as partly implemented in https://github.com/puppeteer/puppeteer/pull/11532

User context should be passed to [`browsingContext.create`](https://github.com/puppeteer/puppeteer/blob/6f828df989666525e1cefcc55ca47d00efe9b2b9/packages/puppeteer-core/src/bidi/BrowserContext.ts#L71) in `BrowserContext.newPage` method