run_test_remote should handle ADBProcessErrors to deal with JavaScript
tests which return non-zero exit codes but should not handle ADBError
or ADBTimeoutError which are indicative of a logic or device error.
run_test_remote should treat ADBProcessErrors due to intermittent
adb communication errors as skipped tests to prevent them from being
misclassified as actual test failures.
run_tests_remote should handle adb errors during device set up and
test runs consistently and issue a failure message which is easily
triaged.
Currently the baseline and via-Ion wasm compilers use MIRType::Pointer to
refer to objects allocated both on the C++ heap and the JS heap, and in fact
to pretty much any flavour of "address of something".
With the introduction of GC support for wasm we need to be much clearer about
which pointers denote a GCable object and which don't. This patch introduces
a new type, MIRType::RefOrNull, to denote GCable pointers in wasm-land, and
converts most but not all existing MIRType::Pointer uses to MIRType::RefOrNull.
The patch was created by auditing all places in WasmBaselineCompile.cpp,
WasmIonCompile.cpp and WasmStubs.cpp, that contain the string
"MIRType::Pointer". Once that was done, various other |switch| statements and
|if| sequences that failed during testing, were fixed up, either by
(1) adding MIRType::RefOrNull as a new case handled the same as the existing
MIRType::Pointer case, or
(2) simply changing the MIRType::Pointer case into the MIRType::RefOrNull case
when it seems that the ::Pointer case is no longer necessary.
--HG--
extra : rebase_source : fc9883265b4563f53b2c1c673b67306eff3ed23d
This file used to only manage the output, but
this is not true anymore, and the name could
be misleading.
We take this as an opportunity to cleanup
some property names and CSS classes.
Differential Revision: https://phabricator.services.mozilla.com/D19135
--HG--
rename : devtools/client/webconsole/webconsole-output-wrapper.js => devtools/client/webconsole/webconsole-wrapper.js
extra : moz-landing-system : lando
Enable mochitest-chrome, but skip test_bug331215.xul and test_bug304188.xul because of frequent intermittent failures on WebRener. The intermittent failures already exist and the failure seems not directly related to WebRender implementation.
Differential Revision: https://phabricator.services.mozilla.com/D19115
--HG--
extra : moz-landing-system : lando
Under certain circumstances, the layout viewport (whose movement triggers the
regular "scroll" events) can end up larger than the visible screen area. In that
case, the scrolling behaviour can become confusing, as small scrolling movements
that aren't affecting the layout viewport's position no longer immediately hide/
show the floating action button and trigger immersive system toolbar mode.
Therefore, AboutReader.jsm needs to watch the *visual* viewport instead, whose
dimensions and position always reflect what is actually visible on-screen.
Differential Revision: https://phabricator.services.mozilla.com/D19263
--HG--
extra : moz-landing-system : lando
This patch:
* Makes LengthPercentageOrAuto generic, and removes a bunch of code fo
LengthPercentageOrNone, which was used only for servo and now can use the
normal MaxLength (with a cfg() guard for the ExtremumLength variant).
* Shrinks MaxLength / MozLength's repr(C) reperesentation by reducing enum
nesting. The shrinking is in preparation for using them from C++ too, though
that'd be a different bug.
* Moves NonNegative usage to the proper places so that stuff for them can be
derived.
I did this on top of bug 1523071 to prove both that it could be possible and
that stuff wasn't too messy. It got a bit messy, but just because of a bug I
had fixed in bindgen long time ago already, so this updates bindgen's patch
version to grab a fix instead of ugly workarounds :)
Differential Revision: https://phabricator.services.mozilla.com/D17762
Also for the intersection observer root margin, since it was easier to fix it
up and clean it up than not doing it.
This is the first big step to get rid of nscoord. It duplicates a bit of logic
in nsLayoutUtils since for now max/min-width/height are still represented with
nsStyleCoord, but I think I prefer to land this incrementally.
I didn't add helpers for the physical accessors of the style rect sides that
nsStyleSides has (top/bottom/left/right) since I think we generally should
encourage the logical versions, but let me know if you want me to do that.
Differential Revision: https://phabricator.services.mozilla.com/D17739
