Open Bug 1795250 Opened 3 years ago Updated 3 years ago

Support running script in Chrome-in-content context (system principal)

Categories

(Testing :: geckodriver, enhancement, P3)

Default
enhancement

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: jgraham, Assigned: jgraham)

Details

Attachments

(1 file)

Pre-fission it was possible to run script in the chrome context using switch-to-context. Post fission that only allows running script in the parent process; we don't have an equivalent of "run script in the content process but with the system principal".

Implementation wise this is basically just passing in sandbox=system.

This adds endpoints:
/session/{sessionId}/moz/execute/sync/chrome
/session/{sessionId}/moz/execute/async/chrome

These allow running script in the content process with the system
principal (vs set context which switches to the parent process).

Assignee: nobody → james
Status: NEW → ASSIGNED
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: