We don't need to initialize SafeBrowsing _immediately_ at startup and we can
wait until the InitLater stage.
This has the added benefit of not crashing xpcshell-test which doesn't have
SafeBrowsing support.
Differential Revision: https://phabricator.services.mozilla.com/D106200
We don't need to initialize SafeBrowsing _immediately_ at startup and we can
wait until the InitLater stage.
This has the added benefit of not crashing xpcshell-test which doesn't have
SafeBrowsing support.
Differential Revision: https://phabricator.services.mozilla.com/D106200
I'm not a fan of accessing private bits like `docShellIsActive` in tests like
that but it's both:
1) very important, if we don't correctly activate docShell performance will be
very poor
2) stable, this API is not likely to change, and if it changes it
should be easy to get whatever the replacement is
Differential Revision: https://phabricator.services.mozilla.com/D94874
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
This is a temporary workaround so that we can test Fission on GeckoView without
implementiong SessionStateAggregator, which needs to be moved to the parent
since Fission implies HistoryInParent.
Differential Revision: https://phabricator.services.mozilla.com/D93865
This patch tightens the coupling between the parent module and the child
actors.
Each parent module will receive messages from the corresponding child actors
whenever the parent actor does not define a message handler.
The parent actor also has the option to handle some messages and delegate the
rest by calling `super.receiveMessage`.
The idea is that every message that can be handled within the browsingContext
should be handled in the parent actor, while everything that needs context
across browsing contexts (e.g. page navigation listeners) should be handled in
the parent module.
Differential Revision: https://phabricator.services.mozilla.com/D89506
When migrating RestoreState to actors we didn't consider that the child actor
gets recreated at every navigation, as its lifetime is tied to the inner
window.
This means that restoring state in one step is not possible, as restoring the
history will trigger a navigation from `about:blank` to the restored page.
To achieve this, we split restoring in two steps and we keep the state on the
parent actor instead of the child.
We move the restoring logic to a newly added GeckoViewContent parent actor,
which is more readibly accessible from both geckoview.js and
GeckoViewContent.jsm.
Differential Revision: https://phabricator.services.mozilla.com/D88637
Eugen Sawin
Agi Sferro
Alexandru Michis
Mark Banner
Brindusan Cristian
Magnus Melin
Edgar Chen
Emilio Cobos Álvarez
smolnar
Anny Gakhokidze
Razvan Maries
Ricky Stewart
Bogdan Tara
Dorel Luca
lonocvb
Gijs Kruitbosch
James Willcox