With a couple of exceptions:
- WebRender, which doesn't support zooming yet
- Windows, which is tracked in bug 1495580
Differential Revision: https://phabricator.services.mozilla.com/D7349
--HG--
extra : rebase_source : 216d8de599b95d28ffd74120aca9b999dab686dc
extra : histedit_source : c206fd9e8046ca7536cc17047a140096d2333617
Double-tap zoom requires that the layout viewport be wider than the screen,
so if we want the test to run on desktop, we need a wide enough layout viewport.
Differential Revision: https://phabricator.services.mozilla.com/D7347
--HG--
extra : rebase_source : e398781447df9de0966ce96a8e540230967d1087
extra : histedit_source : b110e5b26cedb00cec74f44633860be22f654408
Retained displaylists can produce empty paints, which wasn't the case before.
Differential Revision: https://phabricator.services.mozilla.com/D7343
--HG--
extra : rebase_source : a7cce68d6cde3f11aa838609586fd939d428650b
extra : histedit_source : d4e490a445daf01db5ba87185cd0461095f003d7
And also wide enough that the corresponding, proportionally computed, viewport
height is tall enough to allow enough scrolling to bring the iframe under
the cursor.
Differential Revision: https://phabricator.services.mozilla.com/D7342
--HG--
extra : rebase_source : 5b0fee255201cde94dab8faf4b95825f776c76c9
extra : histedit_source : d282542adf2f2678624834e694bbabf095669afa
Previously we would log the displayport and the critical displayport separately,
which made it more difficult to write cross-platform APZ tests.
Differential Revision: https://phabricator.services.mozilla.com/D7341
--HG--
extra : rebase_source : ef2d87b7f9314bb5e6943a8da2b4fd40de85c99b
extra : histedit_source : 80f1e914330f1be0a7a5e531356e6b869b0d29ac
All of its callers are in painting code, so changes will take effect on the
next paint, so there is no need for it to be a Once pref.
Making it Live allows us to selectively enable it in specific mochitests.
Differential Revision: https://phabricator.services.mozilla.com/D7340
--HG--
extra : rebase_source : 772e3c49f5e945d37126979b1c1edab691788e63
extra : histedit_source : 34eccab0c8ab664f15787626bff72f261718ea9c
The assertion is not serving much purpose. Now that container scrolling is
a Live pref, checking it on the compositor side is racy if the pref is
flipped, and on the content side it's clear from the code that it will
only be set to true if the pref is turned on.
Differential Revision: https://phabricator.services.mozilla.com/D7339
--HG--
extra : rebase_source : 4ba80a40969aeac50f303e949472e51d05884fbd
extra : histedit_source : 54c1c0ac5d33a1523080f43ab10c2d01b545a3cc
The GNU_AS check in old-configure depended on running with the value
of $AS before it gets reset to just be the C compiler, which breaks when
we move setting AS into moz.configure.
This patch moves the GNU_AS check to toolchain.configure and changes it
so that it works when the assembler is the C compiler. We do have to
fix things slightly for clang, because the previous check was
succeeding, but not because of clang: it was detecting the presence of
"GNU" in the output for GNU ld/gold and a message about the GNU GPL.
This is a straightforward port of MIDL_FLAGS from old-configure to
moz.configure. The only behavioral change is that it removes support for
prepending MIDL_FLAGS from the environment in configure, but I doubt anyone
uses that.
This is a fairly straightforward port of the AS tool checks from old-configure
to toolchain.configure. AS is a little quirky in that we currently do a
normal-looking check for it, but then override that value to be the C compiler
for non-Windows builds, and ml[64]/armasm64 for Windows builds.
After migrating those checks, the only things left in the MOZ_DEFAULT_COMPILER
macro in compiler-opts.m4 were some unused bits, so I removed them:
* Setting of CPP/CXXCPP, which are set in toolchain.configure now
* Setting HOST_LDFLAGS to empty, which doesn't seem particularly useful.
There was also a quirky old test that the assembler was ml[64] when js-ctypes
is enabled that I removed, I don't think it provides any value since this
patch will ensure that we're using the right assembler for Windows builds.
Since Firefox 41 it has been possible to add a rule with a selector
which does not match an element. The checks of the existence of this
functionality are outdated and can be safely removed.
No supported old versions of Firefox make use of the previous
functionality anymore.
MozReview-Commit-ID: D5ZP09Ckeqd
Differential Revision: https://phabricator.services.mozilla.com/D7597
--HG--
extra : moz-landing-system : lando
This merely centralizes logic that was formerly used at multiple sites
into the single remaining use site.
None of the JAVA* flags have been used for a long time.
Differential Revision: https://phabricator.services.mozilla.com/D7313
--HG--
extra : moz-landing-system : lando
Nicholas Nethercote
Botond Ballo
Tooru Fujisawa
Nathan Froyd
Ted Mielczarek
Eitan Isaacson
Cosmin Sabou
Andrea Marchesini
Ciure Andrei
Razvan Caliman
Gabriel Luong
Xidorn Quan
Tiberius Oros
Daniel Varga
Chris Manchester
Mike Conley
Rob Wood
Ting-Yu Lin
Eliza Balazs
Jeff Muizelaar
Nick Alexander