(In some cases, I've left "ImageLogging.h" being included before the corresponding .h file, because I ran across a warning comment saying that it needs to be included before any IPDL-generated files & anything that includes prlog.h; and it seems possible that Foo.cpp's corresponding Foo.h file could include such headers now or in the future.)
MozReview-Commit-ID: HPvUVj8YuKc
I found these issues locally by moving all of imagelib's .cpp files to SOURCES instead of UNIFIED_SOURCES. (That change isn't part of this patch, though.)
MozReview-Commit-ID: 97Xpfu8eFE6
This is a pre-requisite for moving the `HelperThread` infrastructure over from
using `PRLock` and `PRCondVar` to using `js::Mutex` and `js::ConditionVariable`.
Its needed because waiting on a `js::ConditionVariable` takes the `LockGuard`
for the condvar's mutex as a parameter, so we need to have that accessible. When
we do the conversion, `AutoLockHelperThreadState` will become derived from
`LockGuard` and specialized for the helper thread state lock, and so the guard
will therefore be accessible.
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
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
Previously this implementation would use the expected names of the built-in
module and slot to get a handle on them. This doesn't work on distributions that
use other names. The new implementation searches through the slots from the
default module list for one where PK11_HasRootCerts returns true (which
indicates that NSS considers that slot to contain the default built-in root
list).
MozReview-Commit-ID: LmX27hQfFJU
--HG--
extra : rebase_source : 50383dcc77257fe08ce2c7d908e95cda7c4bbe9d
