Bug 1436841 - Update Intl.RelativeTimeFormat option type: numeric/text to numeric always/auto. r=anba MozReview-Commit-ID: AppMXKfQpG2

Bug 1415951 - Extend TPS to support Addresses and Credit Cards. r=tcsc MozReview-Commit-ID: 8VKBvm60ZSH

Merge mozilla-central to autoland. a=merge on a CLOSED TREE

Bug 1427239 - Always create FormAssistPopup in WebAppActivity; r=droeh Right now we create FormAssistPopup in WebAppActivity based on whether the manifest is successfully loaded. We should always create it because we always try to destroy it in onDestroy(). MozReview-Commit-ID: KskEZmYrDS1

Bug 1434925 - Skip drawing hidden toolbar elements; r=rbarker Apparently a toolbar element can be zero-sized when we try to draw it to the bitmap. We should just skip drawing in that case. MozReview-Commit-ID: LlFQX5uN20h

Bug 1435499 - Guard against OOM when getting toolbar pixels; r=rbarker Guard against OOM errors when getting toolbar pixels, and send a failure message back to compositor when OOM happens. MozReview-Commit-ID: FooZlE979DD

Backed out 3 changesets (bug 1429150) for Android mochitest failures on RobocopTestRunner on a CLOSED TREE. Backed out changeset dbdd43825f46 (bug 1429150) Backed out changeset 23a86891fdaf (bug 1429150) Backed out changeset 1f2d0e869605 (bug 1429150)

Bug 1436800: Update fedora source URL; r=glandium The fedora project is migrating from pkgs.fedoraproject.org to src.fedoraproject.org. We should use the newer URL, particularly because the later has a globally trusted TLS certificate. MozReview-Commit-ID: 7TducICRR0k

Bug 1429150 - Create an enterprise policy to prevent the application from checking for app updates r=Felipe MozReview-Commit-ID: 4K4U4AJw7V1

Bug 1429150 - Make the path to the root of the test data directory available via a pref r=ahal In order to facilitate testing of enterprise policies that must be applied via a JSON at startup, the path to the test data will now be made available during testing. MozReview-Commit-ID: IUhXXsiPRYW

Bug 1429150 - Change nsIApplicationUpdateService::canCheckForUpdates implementation to respect new enterprise policy preventing app update r=Felipe,mhowell MozReview-Commit-ID: 7vPaDbONcRr

Bug 1429195 - Send the selected payment card to the wrapper and DOM. r=jaws MozReview-Commit-ID: 8SqXrnvenGB

Bug 1429195 - Implement and use a <payment-method-picker> custom element. r=jaws MozReview-Commit-ID: 9Ag7debD4IB

Bug 1429195 - Rename basic-card-option attribute names to match autofill storage. r=jaws MozReview-Commit-ID: DFan7RJ6j8R

Bug 1429195 - Add debugging buttons to modify credit card state for payment request. r=jaws MozReview-Commit-ID: Lg6wMft3njy

Bug 1436184 - Remove definitions of Ci, Cr, Cc, and Cu from httpd.js and .sjs files. r=florian MozReview-Commit-ID: IKKb9zr2OSf

servo: Merge #19942 - Use Rect::inner_rect from euclid (from pyfisch:update-euclid); r=emilio Update euclid. Source-Repo: https://github.com/servo/servo Source-Revision: cd663ea33263aaf359bc3d4f78635d1ddfef34c2

Bug 1237454 - Unthrottle transform animations in visibility:hidden element periodically only if the element is scrolled out. r?birtles In the case where we throttle transform animations in visibility:hidden element, we just need to unthrottle only if the element is scrolled out since unlike the scrolled out element, visibility:hidden element keeps invisible even after the element moved into view. MozReview-Commit-ID: 7X2SsOLz4Y5

Bug 1237454 - Throttle animations on visibility:hidden element. r?emilio,birtles,boris This patch does basically throttle animations on visibility:hidden element and unthrottle it once the animating element became visible or a child of the animating element became visible. But still there are some cases that we don't throttle such animations perfectly. For example; div.style.visibility = 'hidden'; // the 'div' has no children at this moment div.animate(..); // The animation is throttled div.appendChild(visibleChild); // The animation isn't throttled visibleChild.style.visibility = 'hidden'; // Now the animation should be throttled again, but actually it's not. To throttle this case properly, when the |visibleChild|'s visibility changed to hidden, we would need to do either 1) Check all siblings of the |visibleChild| have no visible children or 2) The parent element stores visible children count somewhere and decrease it and check whether the count is zero To achieve 1) we need to walk up ancestors and their siblings, actually it's inefficient. 2) is somewhat similar to what we already do for animating images but it's hard to reuse it for CSS animations since it does not take into account that descendants' visibilities. Another example that this patch does not optimize is the the case where animating element has children whose visibility is inherited and the element itself initially visible something like this; let child = document.createElement('div'); // child visibility is 'inherit' div.appendChild(child); div.animate(..); // the 'div' is visible // The animation isn't throttled since the animating element is visible div.style.visiblily = 'hidden'; // Now the animation should be throttled, but it's not since this patch does // not descend down all descendants to check they are invisible or not when the // animating element visibility changed to hidden. This patch adds a test case for this case introduced with todo_is(). Another test case added in this patch fails if we don't use nsPlaceholderFrame::GetRealFrameFor() in HasNoVisibleDescendants(). MozReview-Commit-ID: BJwzQvP9Yc4

Bug 1237454 - Test for an animation on visibility: hidden element which has grandchild. r?boris MozReview-Commit-ID: C0yLy4clwbY