Similar to other tests, the registration process allows workers to activate right after install.
Update web-platform-tests expected data
--HG--
extra : commitid : DpfHRFtmiSz
extra : rebase_source : 4189ef3867c15d9962628a2fa0059a354d234c3e
waitUntil() has been updated to accept multiple calls and concatenate them into Promise.all().
activation does not fail any more even if the promise(s) passed to waitUntil() reject.
Update web-platform-tests expected data
--HG--
extra : commitid : 1jnUWlyw4zQ
extra : rebase_source : 3e2ac14a2f1ebc6fbfc322bb1914feb47f261349
Most of the time the default is to close the browser after tests run. And that can be overridden with
--keep-open. But in some corner cases, the default is to leave the browser open after tests have run.
In these cases, it is not currently possible to override.
This patch allows the syntax --keep-open or --keep-open=false, the latter overrides the edge case
default.
--HG--
extra : commitid : 52IHmZFn1uj
extra : rebase_source : 50ce300ccb08f87e5c9337b945d538c0a17ac04d
The config files under testing/config/mozharness were created so that certain mozharness options
such as test harness arguments could ride the trees, simplifying a lot of logic in mozharness.
But now that mozharness itself is in-tree, these configs no longer serve any purpose. Instead
they are merged into the main configs at testing/mozharness/configs.
--HG--
extra : commitid : KT4Ulv5TsiS
extra : rebase_source : 3cd1284680ddbddf0f1712a985a07579b3905849
extra : source : 28fa968ea46ca3e232b8cfbb4a88e9a492e71b16
Whilst it is not a goal for the Marionette protocol to be fully compatible
with WebDriver due to the different transport mechanisms, bug 1153822
adjusts the Marionette protocol closer to what is prescribed in the
WebDriver specification.
This patch adds support for the new protocol (level or version 2)
to the Python bindings with backwards compatibility for the earlier,
existing protocol (1).
r=jgriffin
--HG--
extra : commitid : CiAKTE3h1nG
extra : rebase_source : ea3ed4ec021febac7f3b2ae2c10ec583a3ddfcff
This required moving the custom mozharness configs out of the builder image
(which puts them in ~, where mozharness no longer looks) and moving them into
mozharness itself.
--HG--
rename : testing/docker/desktop-build/configs/disable_signing.py => testing/mozharness/configs/disable_signing.py
rename : testing/docker/desktop-build/configs/platform_supports_post_upload_to_latest.py => testing/mozharness/configs/platform_supports_post_upload_to_latest.py
extra : commitid : 8FSj0uwFfbE
extra : rebase_source : 949bb94ca58324444981b81e9e9640ab00d63196
extra : amend_source : 40152e06e587728500800de02a437389038fe6ea
extra : source : e3c15b9f89b3c331805b4f1a83f62805f32bbb9a
The config files under testing/config/mozharness were created so that certain mozharness options
such as test harness arguments could ride the trees, simplifying a lot of logic in mozharness.
But now that mozharness itself is in-tree, these configs no longer serve any purpose. Instead
they are merged into the main configs at testing/mozharness/configs.
--HG--
extra : commitid : KJuwMFZEsNB
extra : rebase_source : ebad3073e7ea0e9575582b3355ae17909f7f39a7
The spec for getRegistration() and getRegistrations() states:
"Resolve promise with a ServiceWorkerRegistration object, setting its
service worker client to service worker client, which represents
registration."
indicating a new ServiceWorkerRegistration is created per call. The existing
Blink test depends on Blink's implementation detail which caches the
registration.
--HG--
extra : commitid : JXz3EgFZRo2
extra : rebase_source : e3b1481ac52871759e1526eed9af75c1cb32601a