To match the WebDriver specification error code names, this patch
renames the NoAlertOpenError type to NoSuchAlertError.
Its string error code (the status property) is still correct.
MozReview-Commit-ID: DhWz1tn6DsT
--HG--
extra : rebase_source : dd45387a5869a8df53f20baafe1c683c3af32b25
We currently reduce the precision of timestamps emitted by console.time
in the main context, but not in a Worker. Because web page content cannot
read the content of messages emitted to the console (right?), we don't
actually need to reduce the precision of this data.
MozReview-Commit-ID: EfpIEICy0tX
--HG--
extra : rebase_source : 9516943b11dd7d4ccbcf38a80a981a6fb4662c40
This drops the tests for Marionette protocol level 2. Protocol levels
below 2 were removed some time ago:
https://bugzilla.mozilla.org/show_bug.cgi?id=1409030
MozReview-Commit-ID: GsrdeldnoNH
--HG--
extra : rebase_source : 522d7a9c71545693ca2b662d0a6c715df0f2cd24
To match the WebDriver specification error code names, this patch
renames the NoAlertOpenError type to NoSuchAlertError.
Its string error code (the status property) is still correct.
MozReview-Commit-ID: DhWz1tn6DsT
--HG--
extra : rebase_source : b3da69e566f190c1a016dad7fccf655966779ab1
If Marionette throws inside try...catch block that spawns the TCP
listener, we fail to reset the altered recommended preferences to
their original state, leaving a possibility of tainting the profile.
By calling the uninitialisation code when an error is thrown we
ensure all relevant state gets reset.
MozReview-Commit-ID: XiiIEFMZQY
--HG--
extra : rebase_source : 1a38e446931c916af7f37ffc928683df47f0bba4
Marionette was previously uninitialised when xpcom-shutdown fired.
This may be too late to reset preferences and other state related
to the browser.
This patch moves Marionette to run uninitialisation code on
xpcom-will-shutdown.
MozReview-Commit-ID: 3ytX2k2rrOp
--HG--
extra : rebase_source : 6b9918515b48b2d1166cc985c5d5aeeb82937db0
Setting the MOZ_MARIONETTE environment variable is not a task that
naturally belongs to the TCP listener. This patch moves it to the
Marionette XPCOM component.
MozReview-Commit-ID: 7896Sv91wFy
--HG--
extra : rebase_source : a43335d289c2568f60be3ecc5a9491b2bee27fe9
Setting the recommended preferences is not a task specific to the
TCP listener. It makes more sense to set these in the Marionette
XPCOM component where we manage the Marionette lifetime.
MozReview-Commit-ID: G2RuLhKnX9X
--HG--
extra : rebase_source : 7b3651a682bf86ffe6435dfc35bfce980601aedb
The only thing that cares about it is the frame constructor, it's a shame that
everyone else (in particular, the style system) needs to pay this extra walk
over the DOM.
MozReview-Commit-ID: F7S5zx9KMlp
Turns out that this is a redux issue that was fixed by the redux update (1441147).
Of course, it is bad practice to manipulate state from a non-react component but if there is no warning we can let it go.
MozReview-Commit-ID: 9Ssus7ypvm2
--HG--
extra : rebase_source : 599dfbdcc2a97c6936499b3088400c069c98e022
To get a rid of some methods, I would like to replace nsIDOMNode usages with nsINode.
MozReview-Commit-ID: B0FVczayND0
--HG--
extra : rebase_source : ede058089332202ba0c05ddb61e0f119cbf52fcb
This adds the pref "security.pki.distrust_ca_policy" which, if set to 1,
enforces the graduated distrust from Bug 1409257, and if set to 0 (as it is in
this patch) disables that distrust.
This pref is intended to outlast the Symantec distrust, and instead be able to
extend to enable/disable future root policy actions. It would need its own
tests for that, in the future.
MozReview-Commit-ID: BAZfkapysfX
--HG--
extra : rebase_source : 02b00aa486e9f8efb81b32d38d80db5cae86bc6e
We'll stop dispatching "keypress" event for non-printable keys and key
combinations in the default event group of web content. Therefore,
onbording.js needs to stop handling some keys with "keypress" event listener.
This patch makes add a "keydown" event listener, handleKeydown(), and make it
handle only non-printable keys. Note that we'll keep dispatching "keypress"
event for " " and "Enter". So, we can keep handling them in "keypress"
event listener.
MozReview-Commit-ID: 1jFIv9N03fa
--HG--
extra : rebase_source : 8acabac7ae5c06b527a9fad0fb0fb7b3a2cc5a61