This has been dropped from the spec in:

  https://github.com/w3c/web-animations/commit/17b14a7269c1be263c5525bf42b3892ac80b0938

--HG--
extra : rebase_source : f0c824c5bd5bec7aefbc742830520a3a210468ef

--HG--
extra : rebase_source : 1455cdcb6cabf5e2d4fa65a0d12faa1a4cd700b9

Bug 1342951, part 4 - Add a version of SVGTextFrame::GetSubStringLength that can be used independantly of reflow, to avoid sync reflows. r=heycam

MozReview-Commit-ID: CJqUwF3rXP4

MozReview-Commit-ID: IG2etgpZCHN

MozReview-Commit-ID: A0jxRorD63h

MozReview-Commit-ID: DnpiIUc4RkH

--HG--
extra : amend_source : f768acea169a593bf7313a58378ca4b7c84d4e87

MozReview-Commit-ID: A6mUDNSri2m

--HG--
extra : rebase_source : 43c58d61614e186b89523a301fd1d2d8bd99a503
extra : source : 963bf9d8573273894016e7082cb5f3fb85d80661

Bug 1400453 - yield thread between each call to gExternalProtocolService.getProtocolHandlerInfo; r=florian

--HG--
rename : layout/svg/nsSVGEffects.cpp => layout/svg/SVGObserverUtils.cpp
rename : layout/svg/nsSVGEffects.h => layout/svg/SVGObserverUtils.h

MozReview-Commit-ID: 7VZH3r52Gc7

MozReview-Commit-ID: 5B5W6AHKcCb

MozReview-Commit-ID: Eh11kawjrJB

MozReview-Commit-ID: gZsJeZjJjm

MozReview-Commit-ID: EQlRNgXkc8B

--HG--
extra : rebase_source : b0858ed56fbdf4681163e7b87031409eade26e2f
extra : histedit_source : ceeada7d6e7eab15caf6e4031e2bf44abc5436e4

There's an intermittent that is showing up now that test_register_sign.html
checks state.attestationCert.verify(); to ensure hte SoftToken's certificate
is valid. This patch prints the offending certificate when it's encountered,
to help diagnose the root cause.

MozReview-Commit-ID: 4QSobq9fBGK

MozReview-Commit-ID: FOmIgsEP2fb

MozReview-Commit-ID: EK8iFR1hSRp

MozReview-Commit-ID: BfHhfJKpOOE

MozReview-Commit-ID: GThhGRFgEld

--HG--
extra : amend_source : 59f7e14d32adbfa72f5de2beb04cf67722b9b8fa

MozReview-Commit-ID: 1CvdUz7Uti0

Backed out changesets ef813898b5d3, ce228388aaf6, and c798f482b2c5 (bug 1396098) for violating TC cache constraints

CLOSED TREE

--HG--
extra : amend_source : 84120d6bacb5d72a9fbe41e4c3b405d63825da7c
extra : histedit_source : 8320c2193761b745f10850055ee74a3c9ac73615%2Cfbc2a28d8c5004a53305ef858ca5aea4245691e0

Add a `window` parameter to all Prompt.jsm usages, so the prompt will
appear in the correct window. This includes HelperAppDialog.js, which
was preventing the download chooser dialog from appearing in a custom
tab window.

The patch also moves `getActiveDispatcher` from GeckoViewPermission to
GeckoViewUtils, and makes several improvements to `getChromeWindow` and
`getDispatcherForWindow`. Prompt.jsm now uses the active
WindowDispatcher in the fallback scenario where we don't have a window.

MozReview-Commit-ID: KpAFMCZzQZp

MozReview-Commit-ID: HB5p6Kt0zTb

Bug 1389021 - Force CompositorManagerParent to close before shutting down the compositor thread. r=dvander,me

MozReview-Commit-ID: DYPstPArJWR

Bug 1400386: Skip reftest layout/reftests/font-face/font-display-1.html for being intermittent. r=aryx

MozReview-Commit-ID: 9aEcZg94Ivk

--HG--
extra : rebase_source : 37919c09ea8f9a2ae235ed66246ea26979e9ab4c

MozReview-Commit-ID: 5SmOCzTZiqz

--HG--
extra : rebase_source : 3f75fe0d8efc1fd7f4d671128790e2d0a0d43d57

Bug 1394323 - Remove overflow css rule for 'response-panel' as it prevents scrolling in Console 'Response' tab. r=nchevobbe

MozReview-Commit-ID: GHbYuCfs9L

--HG--
extra : rebase_source : 3daddc00d9e2cc724a3a68024514f64f8f49114e

Now that we have a Docker image with newer library versions on it, we
can move our builds over.  The new images differ from the old
CentOS-based images in two important ways, though:

1) The system compilers in the new image are new enough to be used as
   host compilers; additionally, our CentOS-built GCC compilers will not
   work.  We need to change the Android mozconfigs to reflect that.  We
   also need to change the Android tasks to not depend on the GCC
   toolchain builds.

2) In a similar fashion, we can use the system JDK; we no longer need to
   use the JDK from the Android NDK, which we had packaged up via the
   Android dependencies task.

Both of these changes come with caveats: our l10n repack jobs continue
to run on the CentOS-based images; l10n repacks have not been completely
converted to Taskcluster.  So we need to:

1) Retain the use of our custom GCC toolchain for HOST_CC/HOST_CXX on
   the CentOS-based images.

2) Retain the JDK packages in the tooltool manifests, and referencing
   them when we build on the CentOS-based images.

Now that we have a Docker image with newer library versions on it, we
can move our builds over.  The new images differ from the old
CentOS-based images in two important ways, though:

1) The system compilers in the new image are new enough to be used as
   host compilers; additionally, our CentOS-built GCC compilers will not
   work.  We need to change the Android mozconfigs to reflect that.  We
   also need to change the Android tasks to not depend on the GCC
   toolchain builds.

2) In a similar fashion, we can use the system JDK; we no longer need to
   use the JDK from the Android NDK, which we had packaged up via the
   Android dependencies task.

Both of these changes come with caveats: our l10n repack jobs continue
to run on the CentOS-based images; l10n repacks have not been completely
converted to Taskcluster.  So we need to:

1) Retain the use of our custom GCC toolchain for HOST_CC/HOST_CXX on
   the CentOS-based images.

2) Retain the JDK packages in the tooltool manifests, and referencing
   them when we build on the CentOS-based images.

This seems like the obvious thing to want to happen.

CentOS 6 is pinned to glibc 2.12, but newer Android build-tools (like
aapt) require glibc 2.14.  It's not possible to safely upgrade CentOS
6 distributions to glibc 2.14.

CentOS 7 is pinned to glibc 2.17, which is new enough for newer
Android build-tools. However, I had great difficulty bringing forward
our existing centos:6 Docker image to centos:7.  In particular,
installing recent enough Mercurial, git, Python, and pip versions was
difficult enough that I elected to not pursue this approach.

Instead, I've elected to follow glandium's suggestion from
https://bugzilla.mozilla.org/show_bug.cgi?id=1370119#c5: base on
Debian with snapshots.debian.org for reproducibility.

The most significant changes here:

- using Debian's snapshots repository
- using Python and related tools provided by Debian and baked into the
  build image
- using the JDK and JRE provided by Debian and baked into the build
  image, rather than versions from tooltool (or eventually a toolchain
  build)

Moving the builds over to use this image will follow in the patches
ahead.