Backed out changeset bb1542b364f2 (bug 1364221) for Android 4.2 x86 test_animation_performance_warning.html failures on a CLOSED TREE.

Backed out changeset 8b0e09b6cf8e (bug 1367852) for Windows symbol packaging bustage on a CLOSED TREE.

Bug 1358117 - Add pref to turn on/off leanplum. r=maliu,sebastian MozReview-Commit-ID: 8LHvMPSxAdl

Bug 1350301 - Fix broken layout of dominator view with callstacks enabled; r=fitzgen The shared Frame component appears to set the containing element to be a flex component, while the table view with the dominators expects an inline-block element. This appears to have been broken for quite some time with Bug 1251033. MozReview-Commit-ID: CYkps6QfTJc

Bug 1365975 - Fix pageloader test renaming; r=jmaher MozReview-Commit-ID: IXv2VMR00gr

Bug 1367621 - Regression test to ensure that the URL bar is focused when new tabs are opened in fullscreen mode. r=Felipe MozReview-Commit-ID: 66Rl2U2Kdbl

Bug 1367621 - Make sure to focus the URL bar for 'empty' tabs even while in full screen. r=Felipe In the e10s-case, we might be calling _adjustFocusAfterTabSwitch before updateCurrentBrowser has been called, meaning that mCurrentTab hasn't been updated yet. We use the newTab argument instead. MozReview-Commit-ID: A2ZvbyxSs8t

Bug 1367964 - Skip async tab switching blank tab optimization when the window is minimized. r=billm MozReview-Commit-ID: 676ruHBvFeY

bug 1262812 - use fallback strings in CrashSubmit.jsm so submitting crashes from about:crashes works on Android. r=mconley MozReview-Commit-ID: 3aw17aFysu4

servo: Merge #17042 - Update dependencies (from mbrubeck:always-be-updating); r=jdm No Cargo.toml changes except `base64` which is updated from 0.4.2 to 0.5.2. Does not affect stylo. No new crates in the dependency graph. Source-Repo: https://github.com/servo/servo Source-Revision: 0f5ccdb589f484e17908811173893abc2ac8ff04

Bug 1367852 - Fix symbol dumping for gtest xul.dll r=ted A pdb file name that differs from a dll file name prevents us from dumping symbols for the gtest xul on Windows. This name differed to accommodate fix_stack_using_bpsyms.py failing in the presence of two xul.sym files, which has since been fixed. MozReview-Commit-ID: I5pA5HjMeRe

Bug 1367735 - Do not attempt to generate or install headers or other compile related files during artifact builds. r=mshal This patch stops GENERATED_FILES from being run during export for artifact builds and prevents EXPORTS from being processed because some of these will depend on generated headers. MozReview-Commit-ID: BHZBFbVHwPT

Bug 1350663 - Repaint mask layer when the offset between mask region and mask layer changed. r=mstange Let's said we have a div, <div id="outer" style="width:200px, height:200px; mask="url(opaque-200X100-transparent-200X100.png)""> <div id="innter" style="position:fixed; left:0px; top:0px; width:200px; height:100px; mask-repeat: no-repeat; background-color: blue;"></div> </div> Some hints: 1. '#inner' is out-of-flow 2. '#outer' itself does not draw any things, no background/ border, etc.... 3. Mask applied on '#outer'. 4. opaque-100X200-transparent-100X200.png is a 200X200 image. The upper side of this image is opaque; the lower side of this image is transparent. After page load, you will see a 200X100 blue rect on left-top corner. This blue rect is contributed by 200X100 blue '#inner' and 200X100 opaque upper part of mask. So far so good. Then you scroll down 100px. '#inner' is not moved, since it's an out-of-flow element, mask move up 100px with '#outter'. Ideally, you should see nothing in the view, since '#inner' is now masked by transparent part of the image mask. On FF, you will still see a 200X100 blue rect in view as if no scrolling at all, which is wrong. Here is the root cause of this bug: 1. At beginning, we create a 200X100 mask layer, which fit the size of '#inner'. Not 200X200 of '#outer', since '#outer' basically draw nothing, we smartly choose a more compact draw target for painting the mask. 2. Things go wrong after scrolling down. By scroll down 100px, the size of the mask layer is still "200X100", so we _think_ cached mask layer is still reusable, but it is not. Before scrolling, we paint (0, 0, 200, 100) portion of the 200X200 mask onto mask layer; after scrolling, we should paint (0, _100_, 200, 100) portion of mask onto mask layer. We did not keep this kind of offset information in CSSMaskLayerUserData, so we don't know that the cached mask layer should be rejected. It's difficult to create a reftest for this bug as well. With scrollTo, we may mimic an environment of this error, but since reftest harness will trigger whole viewport repaint while taking a snapshot, we actually can not repro this issue on it. MozReview-Commit-ID: H5xaUSssMRh

Backed out changeset c77265a29cc7 (bug 1358117) for mobile/android/base/java/org/mozilla/gecko/mma/MmaDelegate.java:25: error: cannot find symbol, e.g. in findbugs job. r=backout on a CLOSED TREE

Bug 1362000 - (follow-up) Simplify match logic in CSSMaskLayerUserData::operator==. r=mstange Remove HasUserSpaceOnUseUnitsMaskOrClipPath since it's not necessary. MozReview-Commit-ID: 2sen23m5GjE

Bug 1358117 - Add pref to turn on/off leanplum. r=maliu,sebastian MozReview-Commit-ID: 8LHvMPSxAdl

Bug 1348524 - Remove unused chrome://global/skin/notification/close.png file r=florian MozReview-Commit-ID: 2vh5iExCO9K

Bug 1367830 - Mark hidden window as inactive. r=mystor MozReview-Commit-ID: GJOFjU6WcfG

Bug 1367830 - Refactor to share more code between private and non-private hidden window creation. r=mystor MozReview-Commit-ID: 8NZPbcJtvsE

Bug 1368088 - Add flag to disable code coverage artifact uploading for linux64-ccov. r=jmaher This flag can be used to allow gcov for c++ code coverage to run with '--code-coverage' but it prevents 'gcda' artifacts from being uploaded after the tests are done. The 'gcno' upload is allowed with another flag in the code-coverage config called 'MOZ_CODE_COVERAGE'. Removing it's definition will prevent the 'gcno' file from being uploaded. MozReview-Commit-ID: 1XkH0P4Bh5A