This formats the marionette-harness python tests to be a regular |mach python-test| suite. Though
we add subsuite=marionette, this is just for automation purposes. The new preferred way to run the
marionette harness tests locally is:
./mach python-test testing/marionette
They will also run if running the full suite.
The mozbase packages.txt file modifies mozlog to use 'setup.py' instead of 'pth'. The reason for
this is that the marionette-harness tests use the pytest_mozlog pytest plugin for formatting
their results (converts pytest format into something resembling the standard tbpl logging format).
In order for this plugin to get picked up however, mozlog's setup.py file needs to be processed.
MozReview-Commit-ID: Ata99evHxbd
--HG--
extra : rebase_source : 16ed70edd38a53c3279d8632d7cba3df4d5216c3
This gets raised when trying to run the marionette-harness python tests without an objdir.
It's safe to ignore because mozinfo.json will still be found via the 'dirs' variable which
gets passed in from the marionette harness.
MozReview-Commit-ID: Ata99evHxbd
--HG--
extra : rebase_source : 10731561f644aa563c85ed4a8f70759e64eb4ed2
If the user has deactivated search suggestions (either live suggestions from the search engine or those coming from our history), we shouldn't even bother to restart the corresponding loader in that case, so as to avoid
- wasting processing and network resources
- and perhaps more importantly, not leaking the user's search terms to the default search engine if the user doesn't want that kind of suggestions.
At the moment we only exit early from filterSuggestions() when in private mode or if both kinds of search suggestions have been deactivated, but we don't properly handle the case where only one kind of search suggestions has been deactivated.
This should also improve the display of search history results if the user has deactivated the display of live search suggestions, since currently duplicates between the fresh suggestions and the search history are always removed from the latter even when we're not displaying the former.
MozReview-Commit-ID: IOTMLRaZeyP
--HG--
extra : rebase_source : 331c00c83b18c8e9de3cbb00b92df489c04d7bc0
This makes several of the mix-blend-mode tests pass.
Source-Repo: https://github.com/servo/servo
Source-Revision: 57ff19ec838bf1bbccd6d0dafe069c3351f5b1e5
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 02ac941016a72695f7ded6ef324f30468775ac2a
The "unsupported code directive" is added to the 'ccache -s' output in
b6d7cf5502
We need to teach our parser for it.
MozReview-Commit-ID: IrrJv7I7BVa
--HG--
extra : rebase_source : 025167f75ce8486287d408ccdb3d8113450354cb
On Windows systems an additional chrome window will be opened during startup.
It's used for testing specific GFX related features. It's located off-screen
and will usually be closed immediately. But in some situations it can take longer.
To avoid an inconsistent list of start window handles Marionette should wait
with starting the test until this window has actually been closed.
MozReview-Commit-ID: 3k1hoSYm0Af
--HG--
extra : rebase_source : a2b9bb3c5f375c9142052b41882fbaf890794f33
We have to ensure to switch to the current browser window after closing all the windows
in tearDown.
MozReview-Commit-ID: 3sYwmbew43d
--HG--
extra : rebase_source : 1c37bc56d33e753a29f7f8242b87d224015b4a20
Given that this method will be used in each command for checks of a valid window, we have to return
the currently active window. It means the window mediator should only be used during setting up the
session to find the first browser window.
At the same time the code in this method is getting split-up for chrome and content scopes.
MozReview-Commit-ID: KyzxYk63RgA
--HG--
extra : rebase_source : e21785b1495103056a3b68ccf45054a573f3a967
The "unsupported code directive" is added to the 'ccache -s' output in
b6d7cf5502
We need to teach our parser for it.
MozReview-Commit-ID: IrrJv7I7BVa
--HG--
extra : rebase_source : b3bb6de344e26e7a62fc59f899c45168bafca4ef
MP4Metadata::Metadata() contains the same code at the beginning, so calling
HasCompleteMetadata() is unnecessary, so we should just remove it completely.
(Except to get a better error message, but this will be reinstated in an
upcoming bug.)
MozReview-Commit-ID: 2C3GI5fE0Ja
--HG--
extra : rebase_source : 2bdb6199222dcb0ca4012121a3fd4694b440be3e
When logging a stall a non-existent attribute was attempting to be printed.
This changeset fixes the name being used so that the logging will work
correctly.
Also contains a drive by change to make _video_var_script more consistent.
There was a inconsistency with how objects were referenced which has been
removed.
MozReview-Commit-ID: hTHC9VIxBW
--HG--
extra : rebase_source : 47c65a04c24a1f33888a2034c10c3f54adaa0dc3
macOS oddly sends kVK_ISO_Section instead of kVK_ANSI_Grave when user types left key of Key1 only when the connected keyboard is ISO keyboard. On the other hand, macOS sends kVK_ANSI_Grave instead of kVK_ISO_Section when user types left key of KeyZ only when the connected keyboard is ISO keyboard. So, macOS swapps their key code values only when ISO keyboard is connected.
So, we should treat them as swapped when we compute KeyboardEvent.code value since Chromium treates them as swapped only when computing KeyboardEvent.code value too.
MozReview-Commit-ID: BYeFedydyR5
--HG--
extra : rebase_source : c3bf2a9fefe0e3e98a1955e829243f8fd7d1041a
Andrew Halberstadt
Drew Willcoxon
Dan Minor
Pascal Chevrel
Mike de Boer
Gijs Kruitbosch
Carsten "Tomcat" Book
maliu
Valentin Gosu
Jan Henning
Glenn Watson
JW Wang
Ting-Yu Lin
Henry Chang
Alfredo.Yang
Henrik Skupin
Iris Hsiao
Andrew Swan
Gerald Squelart
Bryce Van Dyk
Masayuki Nakano
Bobby Holley
Xidorn Quan
Zibi Braniecki
Blake Kaplan
Rail Aliiev