They're no longer in the spec, and we and Chrome have supported the up to date
versions for a while.
MozReview-Commit-ID: 3OBpPuua7GW
--HG--
extra : source : d9122e818c36fc0e2381ae469988a96324e5557d
I had meant to remove all of these in bug 1276132, but I missed a couple. We
should now check whether Widevine is enabled before hitting these code paths
by checking the preference.
MozReview-Commit-ID: FmAdlgbF0Py
--HG--
extra : source : 586eff45c5479c7efc86435add5f6e9edd5e43b0
extra : amend_source : 65a9902374155d9e3180f0510b1d1434b986dc83
The refresh driver may not be triggered regularly if the page is static.
In that case, we need to ensure a flush is scheduled for fullscreen
change, otherwise the page may get stuck.
MozReview-Commit-ID: c5FhqaIUQW
--HG--
extra : source : 10269de859e1a6b532ecd02fafff205365c51f2b
Before this patch, there are two issues for non-e10s window:
* The initial entering fullscreen would hit timeout because we do not
record lastTransitionId for entering for non-e10s, and a number is
never larger than undefined, so MozAfterPaint never triggers the
message it should trigger.
* Every exiting fullscreen may hit timeout because when we record the
transition id in DOMFullscreen:CleanUp, the last paint for fullscreen
change may have completed, and consequently we won't receive any new
MozAfterPaint with a larger transition if the page is static.
MozReview-Commit-ID: IWCC6QHA3AL
--HG--
extra : source : 3be19433697e710d33e25f30baf78342ae25d956
In BaseMarionetteArguments._get_preferences, called by verify_usage,
print warning about poorly formatted --pref argument(s)
passed to the mach command, which are ignored.
MozReview-Commit-ID: EQHpvMuB9x8
--HG--
extra : rebase_source : 4bbe35138e96ef3f1c7fe51a0edfbc3ad629b524
In BaseMarionetteArguments.verify_usage, require
total_chunks > 1, as described in error message
(not >= 1 as previously).
MozReview-Commit-ID: 1EftQpfHpo9
--HG--
extra : rebase_source : 6afa71ab2f4677ca1d1f7981ec4427d4c23e9cd6
In BaseMarionetteArguments.verify_usage, some checks for incorrect
usage were printing messages to the console then exiting.
Replace these with `self.error` statements for consistency
and user-friendliness.
MozReview-Commit-ID: 39AYtqiV8Ue
--HG--
extra : rebase_source : e4f152e20f10ba15af6d93a0c69d9d1877f7813e
Nothing in the file requires functionality provided by the CPP unit test harness,
so making the file a GTest makes it more accessible.
MozReview-Commit-ID: FaAtF0blCwV
--HG--
rename : security/manager/ssl/tests/compiled/TestMD4.cpp => security/manager/ssl/tests/gtest/MD4Test.cpp
extra : transplant_source : edV%1F%0B97%1B%25%FA%0ABH%14%F5%A2Ms/%7E
Currently, running all the PSM GTests involves providing a filter that catches
all the various tests. This is annoying and error prone.
The changes here make running all PSM GTests as easy as:
mach gtest "psm*"
MozReview-Commit-ID: EqaysNvwJaQ
--HG--
extra : transplant_source : %0CCM%99%12%18%8D%B9%DD%84%0C%A06%0Ba%AD%A7%EB%B3%FB
MockedOpen monkeypatches os.path.exists. Changes to MockedOpen
since this test code was written have made it more robust
making the extra monkeypatching in the test not necessary.
This change may not fix the test failure reported in the bug.
But at least it makes the test code simpler.
MozReview-Commit-ID: BnUr08leope
--HG--
extra : rebase_source : d8d721392c88883fddf7959ca40ea194f91483c9
In BaseMarionetteArguments.verify_usage, print all missing
test file names before exiting, saving the user from
possibly facing multiple exits one after the other.
MozReview-Commit-ID: 8Q6Ixom1Rrz
--HG--
extra : rebase_source : 391e1f4258ca0bc558e9a4e614d820836c16491a
Given the implementation of BaseMarionetteArguments.parse_known_args,
remove call to parser.parse_args in Marionette mach commands
(marionette-test, session-test,
firefox-ui-update, firefox-ui-functional,
external-media-tests).
Instead, create an argparse.Namespace from the already-parsed
arguments, and pass this to parser.verify_usage.
MozReview-Commit-ID: 20agrkhwlLF
--HG--
extra : rebase_source : 32b0df89c1fbc52af57884d6ba764502b64ac590
