[Fission] Setup Fission Nimbus Experiment Instrumentation
Categories
(GeckoView :: General, task, P2)
Tracking
(firefox133 fixed)
Tracking | Status | |
---|---|---|
firefox133 | --- | fixed |
People
(Reporter: olivia, Assigned: olivia)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid])
Attachments
(1 file)
This bug is to instrument Fission for a Nimbus experiment or rollout.
We will need to find a way to set enviromental variables or else find a way to set the preferences before Gecko is initialized. Connections will need to be setup in Fenix, GeckoView, and Gecko. Will be similar to requirements in bug 1913733, but for the fission side.
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Control:
- Fission - off
Experiment:
- Fission - on
- Strategy -
IsolateHighValue
Assignee | ||
Comment 2•28 days ago
|
||
This patch sets up the Nimbus fission experiment:
- Defines fission.enabled in nimbus.fml.yaml
- Sets fission value based on experiment on GeckoRuntimeSettings builder
- Sets the default WebContentIsolationStrategy of IsolateHighValue for fission
Assignee | ||
Comment 3•27 days ago
•
|
||
For testing:
nimbus-cli --app fenix --channel developer test-feature fission --no-validate /file/path/fission-enabled-false.json
fission-enabled-false.json:
{
"enabled": false
}
nimbus-cli --app fenix --channel developer test-feature fission --no-validate /file/path/fission-enabled-true.json
fission-enabled-true.json:
{
"enabled": true
}
After nimbus cli launches, close and reopen app, and check about:config
for fission.autostart
to match the fission status. (Note: An app reopening is required for the changes to take effect.)
Comment 5•27 days ago
|
||
bugherder |
Description
•