This takes another 21% off the Jetpack test suite run time for me.
MozReview-Commit-ID: 1U2lq4PN21w
--HG--
extra : rebase_source : 1a639e8d920e083ce891312475fcb6fe2f401977
I had to untangle a lot of this mess just to understand what was going on well
enough to make changes.
MozReview-Commit-ID: 2ygiK2ED1pX
--HG--
extra : rebase_source : 95e39c47450b6cecd32cf2a73cdce4b31f5e3e11
This commit introduces a new SDK test addon, which tests the behavior of the
new SDK module "sdk/webextension", and ensures that the provided API can be used
to exchange messages between an SDK module and the WebExtension background page,
and between an SDK module and a WebExtension content script.
MozReview-Commit-ID: jJWfpF3HQM
--HG--
extra : rebase_source : 92c8b02cb2c84dbde3d9e96fe3e48416f382f79d
This commit make it possible the creation of hybrid addons as part of the set of
SDK test addons.
Unfortunately these SDK test addons are build using the old cfx tool and the its
related module loader, and so this patch applies the changes needed to:
- optionally include an `hasEmbeddedWebExtension` option in the generated "install.rdf"
(if the test addon "package.json" contains a property with the same name
in its "package.json")
- initialize the "sdk/webextension" from the bootstrap method params
(as already done in the previous patch for the new SDK module loader)
- include the "webextension/" dir in the generated xpi, if any (similarly
to how it is already done for the "chrome/" dir, which an SDK addon can optionally
contain)
MozReview-Commit-ID: 4WS5ZYkl8FY
--HG--
extra : rebase_source : 287501db8707de2679d3dfffb23555319c706593
This commit integrates the `webExtension` bootstrap method parameter, which can is
set from the XPIProvider when the `hasEmbeddedWebExtension` property is true in the addon
install.rdf, into a new "sdk/webextension" SDK module, to make the creation of
SDK hybrid addons easier.
MozReview-Commit-ID: 4OUPZZyBPJv
--HG--
extra : rebase_source : 32ac6eaa9603604bb110c494019e6c1523c1e731
Instead of creating them in a subdirectory, possibly racing over the
creation of said subdirectory, just create them in the existing current
directory. They're being copied over to some other place anyways, they
just have to be picked from the right location when doing so.
This removes the unnecessary setting of c-basic-offset from all
python-mode files.
This was automatically generated using
perl -pi -e 's/; *c-basic-offset: *[0-9]+//'
... on the affected files.
The bulk of these files are moz.build files but there a few others as
well.
MozReview-Commit-ID: 2pPf3DEiZqx
--HG--
extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204
This removes all of the e10s-related prompting code, including:
- doorhanger offering to opt-in into e10s
- pref and telemetry probe used to measure the number of users who remained opted-in
- dialog that shows up when unchecking the e10s checkbox saying that a tab will open, requesting feedback
- tab opening requesting feedback
- all related strings
The checkbox in the preferences window remains (nightly/aurora only), as well as the message saying that e10s requires a restart.
The e10s accessibility doorhanger remains. and chrome://browser/skin/e10s-64@2x.png remains too because it's also used in the a11y doorhanger.
MozReview-Commit-ID: aOdvnbeHOa
--HG--
extra : rebase_source : e89cc42dddcb376bece435138611b364d3477fa8
