This removes the "session." prefixed global export type in favour
of individually exported types.
MozReview-Commit-ID: 3DHTrJsy2IN
--HG--
extra : rebase_source : 74674f2cc549a245472304c55a14dd2eca1ee235
This removes the "session." prefixed global export type in favour
of individually exported types.
MozReview-Commit-ID: 3DHTrJsy2IN
--HG--
extra : rebase_source : eb2c05c1970c67b5752ece4b916145f053109f69
This change will prefix all log entries originating from a frame
script with the content browser's outerWindowID. That makes it
easier to for example keep of the origin of web DOM event logging.
Whilst it is true that Marionette operates in one browser context at a
time, the frequent context switches make it a cognitive challenge to
keep track of which browser is currently active. This is especially
true at the moment when Marionette does not have the capability to
uniquely identify a browser.
The intention is to change from using the outerWindowID,
which changes when a content browser undergoes a remoteness
change, to using a unique identifier for the browser once
https://bugzil.la/marionette-window-tracking is available.
MozReview-Commit-ID: 813zALY3I9i
--HG--
extra : rebase_source : 559ca853befb2da4a255d59b9525dece962fa357
The "parent process" terminology is already established in the
parent process message manager. This aligns the Marionette component
with this terminology.
MozReview-Commit-ID: 12z1M5jAWDa
--HG--
extra : rebase_source : e735dd5a15c39703cad9799dd7578fed5fb1f139
Calling Cu.importGlobalProperties immediately defines the import
properties and any prototypes that they require. Aside from CPU
overhead, this also tends to consume a lot of memory, especially
for objects with complex prototypes. And it does this once for
every global you call it in. This is especially a problem for
content processes, since we get this memory overhead in each and
every content process.
This patch moves Marionette to use the new
XPCOMUtils.defineLazyGlobalGetters so that symbols are constructed
only when actually needed.
MozReview-Commit-ID: 3RYWTcdO7FM
--HG--
extra : rebase_source : 0c450c8900e5de5446796b34ae4ab6bdf0fe9118
When we traverse up a shadow DOM we pass in null as an indicator to
move upwards. We now check that it is really an element and if not
assume that it is null and move up the tree
MozReview-Commit-ID: AK9eOLFDAgB
--HG--
extra : rebase_source : c748d0fd22d29286f40b78b8790f4a339dfd4299
Prior to bug 1400256 we used to have to deserialise the web
element received from chrome space manually, and presumably this
self-assignment is a leftover from that time.
This fixes an eslint error upon upgrading to eslint version 5.
Thanks-to: Mark Banner <standard8@mozilla.com>
MozReview-Commit-ID: A46wK71AwBe
--HG--
extra : rebase_source : 2ad04f87b31cb369c7c3acf6a50a3bcbd493a735
As a workaround for bug 1411513, about Log.jsm not supporting E10s,
testing/marionette/listener.js makes a synchronous call (sendSyncMessage)
to the main process asking for the Marionette logger repository's level.
We can avoid this blocking operation by using initialProcessData,
which is new since the workaround was implemented.
initialProcessData is a dictionary structured clone serialisable
that gets copied to the content process when it starts. Because the
Marionette log level cannot be changed at runtime it should be fine
to only send this data once per child process.
MozReview-Commit-ID: 3czydqGZpZH
--HG--
extra : rebase_source : 1aaae676d2b56c609844238e8173b64d300e3e00
Adds type checks for the WebDriver:ExecuteScript and
WebDriver:ExecuteAsyncScript commands. This should help prevent
accidental programming mistakes with the Marionette Python client.
MozReview-Commit-ID: JjKgG9OWrdL
--HG--
extra : rebase_source : cd652717f6d4b98d396386e2b971d51a7e737725
This flag is used to turn off the WebDriver spec conforming pointer origin
calculation. It has to be kept until all Selenium bindings can successfully
handle the WebDriver spec conforming Pointer Origin calculation.
MozReview-Commit-ID: 3YknXlWoyi1
--HG--
extra : rebase_source : 6df2af027e7458fd29658d7a3bbe99634b6f58f9
This patch was autogenerated by my decomponents.py
It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.
It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <
Andreas Tolfsen
Coroiu Cristina
David Burns
Jared Wein
Henrik Skupin
Andrew McCreight
Kris Maglione
Cosmin Sabou
Brindusan Cristian
Maja Frydrychowicz
muthuraj90ec@gmail.com
Mark Banner