Closed Bug 1560301 Opened 4 months ago Closed 4 months ago

Implement basic support for Browser context based on container tabs

Categories

(Remote Protocol :: Target, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ochameau, Assigned: ochameau)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

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.

Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dee2008c7a7d
Implement very minimal support of browser context. r=remote-protocol-reviewers,ato
Blocks: 1548596, 1548600
Status: NEW → ASSIGNED
Type: task → enhancement
Priority: -- → P1
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.