Commands which are not defined by the WebDriver spec have to
use the "Marionette" prefix. Exceptions are only allowed for
chrome specific commands which share the same request URL with
the content one.
MozReview-Commit-ID: L47inQ3e8it
--HG--
extra : rebase_source : cc7e03bc01376cc08f6545405a9a54da2a8e77da
The final CC does not happen until after threads are shutdown and so we can't
depend on CC to trigger termination.
This management of the worklet thread by worklet code is an intermediate
situation until worklets run on the threads managed by other objects.
MozReview-Commit-ID: 8hWsdRCppC2
--HG--
extra : rebase_source : 1a0bfdc80ffa2d8beaff6249f40d033a0f319d2e
This will make it possible to migrate existing bindings without also needing to
mass-rewrite frontend code at the same time.
MozReview-Commit-ID: IBBqC4eeDDX
--HG--
extra : rebase_source : e901ac665208b3a683668c1bb33a26dcf479580c
Animation::FlushStyle() gets called only for CSS animations/transitions'
playState changes in JS or ready Promise for CSS animations. In either case
throttled animation state, which is, to be precise, transformed position or
opacity value on the compositor, doesn't affect those results.
The first test case for CSS animations and the first test case for CSS
transitions in this patch fail without this fix.
MozReview-Commit-ID: EVym4qputL4
--HG--
extra : rebase_source : 12524c7db1d59da69687bb123fc65ad4301f5527
The old code would ignore mThresholds if we happened to update when the
observed element was edge-adjacent to its root. This could cause spurious
notifications if it happened to run during a CSS transformation. The new code
more closely follows the spec with a slight deviation where the code treats
all values less than the smallest passed-in threshold as equivalent (when
looking at previousIndex). This matches Chrome's implementation and the tests.
MozReview-Commit-ID: 7oAh1EdjMiY
--HG--
extra : rebase_source : 46de4aee9c7da36bd1b41c07fa9b6bbe8ee15dc0
Use a more specific entry point for the test than
"http://mochitest.test:8888" to make sure that the test is only started
once, when the test opens a tab with the entry point.
MozReview-Commit-ID: 7iAFREDuACu
--HG--
extra : rebase_source : 6ab46b1114dc824f29d0bf21ffa784cd14651447
(Note: this is still disabled by default for non-DevEdition and non-Nightly)
MozReview-Commit-ID: FVgZD3IQSHW
--HG--
extra : rebase_source : b3bac5d476bce61da190655b3bb5c7b044175bb4
Instead of passing a WrPipelineInfo* to C++ code, we can now pass the
WrPipelineInfo directly. C++ code can access the info members without
having to call back into rust code, so the wr_pipeline_info* iterator
methods can be removed. Deleting the structure still requires passing it
back to rust.
MozReview-Commit-ID: HYcPX3mCGKW
--HG--
extra : rebase_source : f4b781cfc463c8e196f67a6e178ce4ce44a9464a
This structure makes it more ergonomic to access vectors from C++. A
Vec<T> can be converted to FfiVec<T> which can safely cross the FFI
boundary. That provides an easy to use read-only access mechanism to the
vector contents. The FfiVec must be returned to rust code to be freed
properly.
MozReview-Commit-ID: AdIyEsjrPSZ
--HG--
extra : rebase_source : db87eb55e19c2d129f4c8a8155b03d9fbfc98199
We need to side-step existing cross-origin checks in Performance Timing code
when the caller is a web extension content script that otherwise has permission
to access the cross-origin resource.
MozReview-Commit-ID: 8IgtqZgPWgY
--HG--
extra : rebase_source : e8152c5d8ab32096d1ff7f97311c1b43b57c3694
Ben Kelly
Jason Laster
Nathan Froyd
Geoff Brown
Razvan Caliman
Gurzau Raul
Lee Salzman
Johan Lorenzo
Nicolas Chevobbe
Kartikaya Gupta
Luca Greco
Marco Bonardo
Margareta Eliza Balazs
Gabriele Svelto
Henrik Skupin
Karl Tomlinson
Brian Grinstead
Thom Chiovoloni
Edouard Oger
Hiroyuki Ikezoe
Blake Kaplan
Kris Maglione
Kit Cambridge
Rob Wu
William Lachance
Mike Taylor
Tim Nguyen
Tomislav Jovanovic
Zibi Braniecki