1560301 - Implement basic support for Browser context based on container tabs

Status: RESOLVED FIXED

(Remote Protocol :: CDP, enhancement, P1)

Description

[Alexandre Poirot [:ochameau]]

Puppeteer's tests depends on browser context, being created via Target.createBrowserContext. We then have to support browserContextId in various methods/events.

Based on Andrey's experience, we know that container tabs have some limitation around cookies (at least), which do not match puppeteer's expectations/chrome implementation of browser contexts.
But container tabs are, by far the closest way to have distinct navigation contexts without spawing mutliple profiles and firefox instances.

So we will try to mimic what has been done in Juggler and engage a discussion with gecko developers to see if we can fix the discrepancies with chrome.

Comment 1

[Alexandre Poirot [:ochameau]]

Attachment: Bug 1560301 - Implement very minimal support of browser context.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/dee2008c7a7d
Implement very minimal support of browser context. r=remote-protocol-reviewers,ato

Comment 3

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/mozilla-central/rev/dee2008c7a7d