This never actually worked, because nothing ever listened to the notification
sent in XPCJSContext (kill-content-script-sandbox). We're also removing the
"Temporarily disable extension" button in the slow addon notification, which
was the primary caller of this - however, that's in a separate patch.
Differential Revision: https://phabricator.services.mozilla.com/D110583
The code as written does not remove the connection from both
mContentConnections and mNonStartedContentConnections since && short circuits.
Since the connection is always present in mContentConnections, we just check
that.
Differential Revision: https://phabricator.services.mozilla.com/D109443
This service, based off of TestRunnerActivity, can be used to run an
xpcshell-test instance.
It supports up to 10 concurrent instances, although we can add more if we need
to.
Local testing indicates that with more than 4 concurrent instances there's not
gain in test running performance.
This also adds a new intent action
|org.mozilla.geckoview.test.XPCSHELL_TEST_MAIN| that can be used by the test
harness to start the main application and gain foreground priority without
starting Gecko (which would interfere with the xpcshell runner services).
Differential Revision: https://phabricator.services.mozilla.com/D106212
This commit adds a new command line option |-xpcshell| that, when passed, will
run an xpcshell instead of launching a full Gecko instance.
This command line option is restricted to org.mozilla.geckoview.test for now,
as it's really hard to use and not really a usecase outside mozilla. We can
revisit this if there's interest.
Differential Revision: https://phabricator.services.mozilla.com/D106211
When getting the *-extension-installed messages we should always notify
GeckoViewWebExtension.
This currently works because we always install the test support extension which
causes us to initialize GeckoViewWebExtension. On xpcshel tests, however, there
is no support extension so we need to account for that in GeckoViewStartup.
Differential Revision: https://phabricator.services.mozilla.com/D106319
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
The code as written does not remove the connection from both
mContentConnections and mNonStartedContentConnections since && short circuits.
Since the connection is always present in mContentConnections, we just check
that.
Differential Revision: https://phabricator.services.mozilla.com/D109443
This service, based off of TestRunnerActivity, can be used to run an
xpcshell-test instance.
It supports up to 10 concurrent instances, although we can add more if we need
to.
Local testing indicates that with more than 4 concurrent instances there's not
gain in test running performance.
This also adds a new intent action
|org.mozilla.geckoview.test.XPCSHELL_TEST_MAIN| that can be used by the test
harness to start the main application and gain foreground priority without
starting Gecko (which would interfere with the xpcshell runner services).
Differential Revision: https://phabricator.services.mozilla.com/D106212
This commit adds a new command line option |-xpcshell| that, when passed, will
run an xpcshell instead of launching a full Gecko instance.
This command line option is restricted to org.mozilla.geckoview.test for now,
as it's really hard to use and not really a usecase outside mozilla. We can
revisit this if there's interest.
Differential Revision: https://phabricator.services.mozilla.com/D106211
When getting the *-extension-installed messages we should always notify
GeckoViewWebExtension.
This currently works because we always install the test support extension which
causes us to initialize GeckoViewWebExtension. On xpcshel tests, however, there
is no support extension so we need to account for that in GeckoViewStartup.
Differential Revision: https://phabricator.services.mozilla.com/D106319
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
Csoregi Natalia
David Parks
Agi Sferro
Doug Thayer
Andreea Pavel
Karl Tomlinson
Alexandru Michis
Tim Huang
Dylan Roeh
Simon Giesecke