This test was failing intermittently on GeckoView e10s. The
waitForAnimationReadyToRestyle helper works around certain cases where, due to
vsync, the animation ends up starting at exactly the same frame time as when it
was created meaning that restyling may not get triggered and hence we won't have
a chance to send it to the compositor.
It's not clear why this happens more frequently on GeckoView e10s but this seems
to fix the failures anyway.
Differential Revision: https://phabricator.services.mozilla.com/D18043
--HG--
extra : moz-landing-system : lando
Now that we decide whether the collection will be incremental or
non-incremental before taking the session lock, we can tighten these
assertions.
Differential Revision: https://phabricator.services.mozilla.com/D18021
--HG--
extra : moz-landing-system : lando
PresShell::HandleEvent() treats capturing content only when received event is
related to pointing device. And it's used in 2 purposes. One is for computing
to target document of coming event. The other is for handling events using
coordinates. Therefore, if we create a helper method to retrieve it, we can
move the variable into smaller blocks.
Differential Revision: https://phabricator.services.mozilla.com/D16954
--HG--
extra : moz-landing-system : lando
This test seems fragile and report leaks when run sequentially with other tests.
Destroying its toolbox and more importantly waiting for it to complete seems to
stop the leaks.
Depends on D17925
Differential Revision: https://phabricator.services.mozilla.com/D17926
--HG--
extra : moz-landing-system : lando
BrowsingContextTargetActor, which is calling `_detach` expects it to return `true`
if everything worked as expected. But the overloaded method in ParentProcessTargetActor
was always returning `undefined`.
Depends on D14957
Differential Revision: https://phabricator.services.mozilla.com/D17925
--HG--
extra : moz-landing-system : lando
When debugging contexts running from the system compartment, the debugger has
to be loaded in a dedicated Loader, with invisibleToDebugger flag turned on.
This ensures that the Debugger API is going to be used from a distinct system
compartment. Otherwise it may be used from the same compartment than the page
we are debugging.
Differential Revision: https://phabricator.services.mozilla.com/D14957
--HG--
extra : moz-landing-system : lando
We reenable the corresponding tests unconditionally because we don't run
tests on the msvc builds anyways (and they're going to be retired soon).
Differential Revision: https://phabricator.services.mozilla.com/D18028
--HG--
extra : moz-landing-system : lando
Because of spinning out from PresShell::EventHandler::HandleEvent(), we can use
early-return style in MaybeHandleEventWithAccessibleCaret(). This patch
rewrites MaybeHandleEventWithAccessibleCaret() with the style.
Differential Revision: https://phabricator.services.mozilla.com/D16953
--HG--
extra : moz-landing-system : lando
We can replace it by a simple for-loop. If we want to print not only the
tag, but the detailed frame information, we can use nsFrameList::List().
Differential Revision: https://phabricator.services.mozilla.com/D17734
--HG--
extra : moz-landing-system : lando
Many of the modifications are guarded by #ifdefs. I verify them locally
by manually define them in nsBlockDebugFlags.h and nsLinelayout.cpp.
Note that I replace "mFrame" with "frame" in lines guarded by
NOISY_BLOCK_DIR_MARGINS in nsBlockFrame.cpp because they were
incorrectly renamed in Bug 1277129 Part 6a.
https://hg.mozilla.org/mozilla-central/rev/a70b04f074fc
Differential Revision: https://phabricator.services.mozilla.com/D17733
--HG--
extra : moz-landing-system : lando
In Android the embedded GeckoView can be in a scrolling parent, and move
along with the user's finger. In order to intepret touch movements for
gestures, we need to account for the device position of each touch.
Differential Revision: https://phabricator.services.mozilla.com/D17045
--HG--
extra : moz-landing-system : lando
We currently use ParentLayer pixels in GestureEventListener, it should
be Screen pixels because we care about physical distances and
thresholds, not layer-relative ones.
Differential Revision: https://phabricator.services.mozilla.com/D17042
--HG--
extra : moz-landing-system : lando
In Bug 1522354, the default for `--host` was changed to detect running on a 64bit host.
Since `--target` defaults to `--host`, this changed the default for `--target`
as well. This didn't affect builds, as they explictly set the `--target` in
`build/win32/mozconfig.vs2017`. Set it explicitly in L10n builds as well.
Differential Revision: https://phabricator.services.mozilla.com/D17967
--HG--
extra : rebase_source : 80bd3609ae29be0748d56be407c4d95443e256a0
extra : amend_source : c56db8fe0f680d0b4f9f14e24269799c76646203
There are three different APIs that serve similar purpose. Keeping only
one is sufficient.
Differential Revision: https://phabricator.services.mozilla.com/D17732
--HG--
extra : moz-landing-system : lando
