When the session storage prefs are enabled, GeckoSession updateSessionState will provide the bundle of information, including zoom, scroll, and form data, to the delegate. Currently works for Fission and on Fenix.
Differential Revision: https://phabricator.services.mozilla.com/D148215
This commit arranges to write `targeting.snapshot.json` to the local
profile directory every 30 minutes, and just before shutdown. For
simplicity, it uses the existing `JSONFile.jsm` implementation.
Differential Revision: https://phabricator.services.mozilla.com/D151057
`browser.privacySegmentation.enabled` is going to be set when users opt into Felt Privacy. When I originally wrote some of this code I naively used it to pref things on, on the assumption that there would never be a situation where it would be `true` before 106 (when we remove the pref-off for this work).
However, we want to run an experiment with pinning private browsing to the taskbar ahead of 106. To avoid any possibility of accidentally opting users into Felt Privacy without their consent, let's use a distinct pref for turning these features off for now. This pref will disappear in the 106 cycle, as none of this code needs to be behind one at that point - so I don't _think_ this needs to go in `firefox.js`.
Differential Revision: https://phabricator.services.mozilla.com/D151065
The Nimbus Features corresponding to FxMS messaging surfaces are actually
intended to map to FxMS message groups, which can accept *any* FxMS message.
The features have been updated with schemas that accept any FxMS message.
As part of this, all FxMS schemas have been updated with an `$id` so that they
can be bundled into feature schemas and have their internal `$ref`s work.
(Otherwise, a `$ref` would be relative to the top-level schema instead of the
sub-schema).
Schemas for individual message types are no longer exposed as resource:// URIs,
except in tests, as indivual schemas are no longer required at runtime.
Additionally, each FxMS schema has had its `template` field become required and
requires a constant value for that schema (e.g., Spotlight requires a template
value of "spotlight").
A test has been added to ensure that if any of the messaging surfaces schemas
change that the feature schemas are also updated. The feature schemas can be
regenerated via:
```
cd ./browser/components/newtab/content-src/asrouter/schemas
../../../../../../mach make-schemas.py
```
Differential Revision: https://phabricator.services.mozilla.com/D147332
This preference drives the "Show user agent" feature accessible from the RDM options.
Flipping it to true will make the User agent input visible on all channels by default, but the feature itself was already available everywhere.
You just had to first select "Show user agent" in devedition/beta/release to show the input. I think the feature is useful enough to enable it by default.
Also we run all our tests with the preference forced to true.
Differential Revision: https://phabricator.services.mozilla.com/D150455
When the session storage prefs are enabled, GeckoSession updateSessionState will provide the bundle of information, including zoom, scroll, and form data, to the delegate. Currently works for Fission and on Fenix.
Differential Revision: https://phabricator.services.mozilla.com/D148215
When the session storage prefs are enabled, GeckoSession updateSessionState will provide the bundle of information, including zoom, scroll, and form data, to the delegate. Currently works for Fission and on Fenix.
Differential Revision: https://phabricator.services.mozilla.com/D148215
This new feature will only work in the "MBT", when devtools.browsertoolbox.fission is true.
It is based on yet another preference, devtools.browsertoolbox.scope,
which is meant to be toggle by DevTools UI only (see next patches).
When the new pref is set to "everything", we will observe FRAME and PROCESS targets
and so debug everything running in content processes.
But when it is set to "parent-process", we will only observe WORKER
and be restricted to parent process resources only.
Differential Revision: https://phabricator.services.mozilla.com/D146891
Write the deelevation-status enum value into the parent process, where
it will (hopefully) show up in the event of a crash report.
(Presenting this value more conveniently -- _e.g._, in `about:support`
and/or Firefox telemetry -- would require additional plumbing, and so
has been left to future work.)
Depends on D149545
Differential Revision: https://phabricator.services.mozilla.com/D149546
Add a new command-line flag `--attempting-deelevation` which prevents
the launcher from entering an infinite loop of deelevation attempts.
Additionally, produce an enum value indicating the decisions made by the
launcher process. (Nothing is done with this value yet; that will happen
in the following commit.)
Depends on D149544
Differential Revision: https://phabricator.services.mozilla.com/D149545
"Firefox" may be inaccurate if the current app is, e.g., "Thunderbird",
or some alternatively-branded fork of Firefox.
Also, specify the Launcher as being the event source. (Officially this
should be handled via an appropriately-declared facility identifier, but
that would involve an additional build step invoking a compiler not
distributed with the ordinary Windows SDK.)
Differential Revision: https://phabricator.services.mozilla.com/D149544
This new feature will only work in the "MBT", when devtools.browsertoolbox.fission is true.
It is based on yet another preference, devtools.browsertoolbox.scope,
which is meant to be toggle by DevTools UI only (see next patches).
When the new pref is set to "everything", we will observe FRAME and PROCESS targets
and so debug everything running in content processes.
But when it is set to "parent-process", we will only observe WORKER
and be restricted to parent process resources only.
Differential Revision: https://phabricator.services.mozilla.com/D146891
Highlights
- Network monitoring is turned off by default in browser console/ browser toolbox console on initial load.
- A new "Enable Network Monitoring" setting is added to enable users toggle on an off as they desire.
- The user setting is persisted across toolbox reopens.
Differential Revision: https://phabricator.services.mozilla.com/D145234
Highlights
- Network monitoring is turned off by default in browser console/ browser toolbox console on initial load.
- A new "Enable Network Monitoring" setting is added to enable users toggle on an off as they desire.
- The user setting is persisted across toolbox reopens.
Differential Revision: https://phabricator.services.mozilla.com/D145234
