When moving from mozreview to Phabricator, the old mozreview git hook
had to be removed. Logic to automate the removal of this hook was added
to vcs-setup.
This commit removes this automated removal since it has been 2 years
since it landed.
Differential Revision: https://phabricator.services.mozilla.com/D82125
Depends on D81677
We recently introduced a modification to updateWorkers in order to swallow errors after destroy.
Since I am suggesting to add a helper to take care of a similar issue in Toolbox::highlight I think we could also apply it here.
Differential Revision: https://phabricator.services.mozilla.com/D81679
We very often have to introduce a pattern in our async methods in order to "swallow"
async errors if a panel was destroyed, if the toolbox was destroyed etc...
This is not an issue in a regular usage of the toolbox, but it can lead to many intermittent failures.
One solution could be to always wait for all requests to be completed before shutting down tests.
Another approach is to have an easy way of swallowing errors when a certain condition is true.
The helper added here will run the provided method in a try catch, and will only bubble up errors if the provided check fails.
Differential Revision: https://phabricator.services.mozilla.com/D81675
- Adds a new "extensions.serviceWorkerRegister.allowed" pref (defaults to false)
- Makes ServiceWorkerContainer::Register to throw NS_ERROR_DOM_SECURITY_ERR if the
script url is a moz-extension url and the caller is a non-system caller
(but do not throw NS_ERROR_DOM_SECURITY_ERR if the caller is a moz-extension
and the new pref is set to true)
Depends on D60244
Differential Revision: https://phabricator.services.mozilla.com/D60245
- Adds the new about:config pref "extensions.backgroundServiceWorker.enabled" (currently defaults to false).
- Adds the background.service_worker property to the manifest JSON schema definition
- Locks background.service_worker manifest property behind the new preference
- Adds a new BackgroundWorker class to ext-backgroundPage.js (responsible for managing the background
service worker for the extension, e.g. make sure that the expected worker script is registered
as expected when the extension is starting up)
- Adds to the ServiceWorkerManager a new method to allow the WebExtension Framework to register the
background service worker without an existing extension page
- Allows the "moz-extension" schema in the dom/serviceworkers and dom/cache internals
Depends on D63697
Differential Revision: https://phabricator.services.mozilla.com/D60244
For now this only handles the initialisation routines. Loading from cache still creates a plain SearchEngine class, and as a result updates handling is still in the main SearchEngine class.
Depends on D80498
Differential Revision: https://phabricator.services.mozilla.com/D81696
Automatic update from web-platform-tests
Python 3: port tests of range, stale-while-revalidate in fetch (#24423)
* Python 3: port tests of range, stale-while-revalidate in fetch
* Remove unnecessary prefix and use bytes type for content_range
--
wpt-commits: b13c1d42b3aaf52a4e7b0b18795aeefb17a62eb6
wpt-pr: 24423
Automatic update from web-platform-tests
Implement CSPEE Blanket Enforcement logic out-of-blink
This changes adds to the AncestorThrottle a check for the step
"Does response allow blanket enforcement of policy from request" of
Content Security Policy: Embedded Enforcement:
https://w3c.github.io/webappsec-cspee/#origin-allowed Behind the flag
This is one of the steps of moving CSPEE out-of-blink and is hidden
under the flag network::features::kOutOfBlinkCSPEE.
Change-Id: Id3092322134e055810d4006e63e6974ee64315be
Bug: 1094909
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218019
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784753}
--
wpt-commits: 8a3698a69e785aefc5c83ea2e348fd3350bfa43a
wpt-pr: 24311
Automatic update from web-platform-tests
Move asserts inside the test (#24421)
Failing one of these asserts would otherwise result in a harness error.
--
wpt-commits: f5c167568d5f5c02ef9a3b3131c64f3a254c2296
wpt-pr: 24421