This prepares for the removal of the "listbox" element and binding.
MozReview-Commit-ID: G1OxRGBphmw
--HG--
extra : source : 65d7ca38bd086abe7df0e50e9e5a9ba1d70202c3
Summary: GTest is permafailing because of this test (GTest is always running over 1200s).
Reviewers: froydnj
Reviewed By: froydnj
Bug #: 1473531
Differential Revision: https://phabricator.services.mozilla.com/D2032
--HG--
extra : rebase_source : 07413c4d7ba4eb6bd1439f292bd489a775dab61b
Automatic update from web-platform-testssensors: Fix flakiness in the same-origin access check tests
Commit f73dfaffe ("[sensors] Check that sensor frame and focused frame of
same origin") added a few same-origin access check tests for sensors in
generic-sensor-iframe-tests.sub.js.
The test that checks that a sensor is not suspended when focus changes to
another same-origin frame was flaky though, especially on the Mac bots.
The actual fix is a one-liner: we were missing a call to Sensor.stop() so
that the sensor in the top-level document wouldn't continue to push
'reading' events to our EventWatcher while we were waiting for the
"is_sensor_suspended" command to be processed in iframe_sensor_handler.html.
I'm also taking the opportunity to make a few other minor improvements:
* Fix a few typos in the comments, and improve the comment explaining why we
can end up sending more "reading" events than originally expected.
* Create the sensor belonging to the top-level document with a higher
frequency than the default 5Hz. This makes it a lot easier to reproduce
the error we were having and will hopefully make the test consistently
fail in the future instead of being flaky should another related bug
occur.
* Make the EventWatcher instances we create also watch for "error" events;
if an error event ever gets sent, the test should now fail instead of just
timing out waiting for a "reading" event that is never delivered.
Bug: 855222, 857520
Change-Id: I945bb19d74e608089aa9aee82a4e74e05fae37ae
Reviewed-on: https://chromium-review.googlesource.com/1127048
Commit-Queue: Raphael Kubo da Costa (CET) <raphael.kubo.da.costa@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573062}
--
wpt-commits: 4b54599775c8cee2a482bd5f6f208f575b80bf7b
wpt-pr: 11807
Automatic update from web-platform-testsXRDevice should not extend EventTarget.
The spec removed any events that were fired on the XRDevice a while ago,
but our implementation forgot to clean this up.
Bug: 859706
Change-Id: I086813a5a2cbf6ebbf7faf576b066fa3957ad5dc
Reviewed-on: https://chromium-review.googlesource.com/1123645
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573048}
--
wpt-commits: 323ad5914427ec5f898837a00f0ee355c70082a3
wpt-pr: 11774
Automatic update from web-platform-testsRename ServiceWorker to service-workers and update (#11821)
--
wpt-commits: dbd7ce9488cd0cfdf0f9a1ea7d949eb448327f36
wpt-pr: 11821
Test verification backfill specifies --gpu-required for certain types
of tests (depending on test path and/or suite). web-platform-tests do
not recognize --gpu-required. This patch updates the backfill logic
to avoid --gpu-required for wpt.
Apparently a prehistoric server implementation would send a
certificate_authorities field that didn't include the outer DER SEQUENCE tag, so
PSM attempted to detect this and work around it. Telemetry indicates this is
unnecessary now: https://mzl.la/2Lbi1Lz
--HG--
extra : rebase_source : 6669586d657efb243070a4ceb231583b40823543
extra : amend_source : e87f7c84c6c1a51637914bde5950268409b70571
Bug 1447977 introduced a new implementation of evaluate.isCyclic
that was not based on JSON.stringify to overcome cyclic references
stored on Element prototypes.
This patch reverts the new behaviour and hides it behind an environment
variable MOZ_MARIONETTE_NEW_CYCLIC. This is useful so we can more
easily test the difference in automation.
MozReview-Commit-ID: 2xtNL596Imc
