In idlharness.window.js, ResizeObservation is not an public interface in
the current spec, so the test should be updated.
In eventloop.html, unfortunately, there are two issues:
1. The test framework will be timeout if there is any `assert_equals()`
failed. We should rewrite it.
2. Actually, we only have one failure in this test file:
`assert_equals(helper.rafCount, 1, "new loop");` in test0. We fire
this event in the next Tick(), but we call the callback of
`requestAnimationFrame()` after several Tick()s, so `helper.rafCount`
is still 0 in this case. This may be a bug of the test because using
`requestAnimationFrame()` cannot reflect the next event loop, or our
scheduling of ResizeObserver is not correct.
Note: this assert_equal() was added by Google, not by Fariskhi.
Differential Revision: https://phabricator.services.mozilla.com/D27619
--HG--
extra : moz-landing-system : lando
Othewise subsequent test cases would be affected by the change for
'vertical-rl'.
Depends on D28754
Differential Revision: https://phabricator.services.mozilla.com/D28755
--HG--
extra : moz-landing-system : lando
It turns out there are several places where the change to suite 'jittest-chunked'
causes problem. I am abandoning that approach.
Desktop uses this trick, and this returns android '-chunked' handling to a state
similar to what it was before I started messing around!
Differential Revision: https://phabricator.services.mozilla.com/D28897
--HG--
extra : moz-landing-system : lando
This whitelisting is not as mangled as the old one, so hopefully it
will be more resilient to changes in the Rust compiler. I moved them
to the top level white list, because like with the JS leaks we are
mostly focused on C++ leaks. Any interesting Rust leak is probably due
to a C++ leak.
Differential Revision: https://phabricator.services.mozilla.com/D28727
--HG--
extra : moz-landing-system : lando
The format of platform and type data seems to have evolved over time; these
changes seem to handle the new formats well.
Differential Revision: https://phabricator.services.mozilla.com/D28766
--HG--
extra : moz-landing-system : lando
I still haven't managed to verify this on try, but it seems like the best
explanation for the timeouts.
Differential Revision: https://phabricator.services.mozilla.com/D28762
--HG--
extra : moz-landing-system : lando
Fixed width and height is not a strong enough condition.
min/max-width with intrinsic size keywords makes the final size of the image
also depend on the intrinsic size. Don't optimize away reflows when the
intrinsic size changes if they're used.
Differential Revision: https://phabricator.services.mozilla.com/D28720
--HG--
extra : moz-landing-system : lando
We do want to record soft break opportunity after a frame whose content can't
be part of the existing in-flow text run, since this normally should be a text run
boundary. However, though an out-of-flow frame can't be part of the existing
in-flow text run, it also doesn't break it either. In fact, the texts after the
out-of-flow frames are able to continue the existing in-flow text run. So,
introducing a line-break-after opportunity in this case may cause an unexpected
line break for every out-of-flow frame.
In this patch, we add a condition to prevent us from recording soft break
opportunities for out-of-flow frames.
Differential Revision: https://phabricator.services.mozilla.com/D28625
--HG--
extra : moz-landing-system : lando
We do want to record soft break opportunity after a frame whose content can't
be part of the existing in-flow text run, since this normally should be a text run
boundary. However, though an out-of-flow frame can't be part of the existing
in-flow text run, it also doesn't break it either. In fact, the texts after the
out-of-flow frames are able to continue the existing in-flow text run. So,
introducing a line-break-after opportunity in this case may cause an unexpected
line break for every out-of-flow frame.
In this patch, we add a condition to prevent us from recording soft break
opportunities for out-of-flow frames.
Differential Revision: https://phabricator.services.mozilla.com/D28625
--HG--
extra : moz-landing-system : lando
With this change tooltool.py also supports taskcluster credentials to be passed
(in json format) to --authentication-file option. RelengAPI tokens are still
working with this patch, just additional authentication is added.
Differential Revision: https://phabricator.services.mozilla.com/D27881
--HG--
extra : moz-landing-system : lando
Mark a few linux debug non-e10s tests as expected fail as this change seems to break these tests in weird ways in that configuration.
Differential Revision: https://phabricator.services.mozilla.com/D28160
--HG--
extra : moz-landing-system : lando
This patch leaves wpt running against fennec on androidx86 as tier2, adds wpt to run against geckoview testactivity on android x86_64 as tier3, and adds enough metadata to run_info_extras to help differentiate the two in expectation files. Fennec is "os == android and not e10s", while geckoview is "os == android and e10s".
Differential Revision: https://phabricator.services.mozilla.com/D27182
--HG--
extra : moz-landing-system : lando
Mark a few linux debug non-e10s tests as expected fail as this change seems to break these tests in weird ways in that configuration.
Differential Revision: https://phabricator.services.mozilla.com/D28160
--HG--
extra : moz-landing-system : lando
