Bug 1429298 - Part 5: Implement BuildPath for offset-path. r=jwatt Implement one variant of BuildPath to accept nsTArray<StylePathCommand>, which is used by <offset-path> (and clip-path in the future). Depends on D3922 Differential Revision: https://phabricator.services.mozilla.com/D2967

Bug 1429298 - Part 4: Rename builder as aBuilder in SVGPathData.cpp. r=TYLin Follow the rule of naming for the function parameters. Depends on D2966 Differential Revision: https://phabricator.services.mozilla.com/D3922

Bug 1429298 - Part 3: Use macro for path parser. r=emilio There are a lot of duplicates, so we use macro to refine them. Depends on D2963 Differential Revision: https://phabricator.services.mozilla.com/D2966

Bug 1429298 - Part 2: Define offset-path and implement it in style system. r=emilio Define OffsetPath & SVGPathData on the servo-side, and StyleMotion & StyleSVGPath on the gecko-side. We parse the SVG Path string into a vector of PathCommand. To build the gfx::Path, we will convert it into gfx::Path later in a different patch. The basic flow is: - Parse SVG Path String into SVGPathData (in Rust). - Use cbindgen to make sure the layout of PathCommand and StylePathCommand, and then set the Box[PathCommand] into nsTArray<StylePathCommand>. - Try to convert nsTArray<StylePathCommand> into gfx::Path. (This part will be implemented in a different patch.) Finally, we use the gfx::Path to create a motion path transform. The layout implementation is in the later patch. Depends on D2962 Differential Revision: https://phabricator.services.mozilla.com/D2963

Bug 1429298 - Part 1: Define the preference for motion-path. r=emilio Define the preference. I will enable it only for debug usage and test coverage in a different patch. Differential Revision: https://phabricator.services.mozilla.com/D2962

Bug 1482220 - Listen for the autofill edit forms being appended for localization. r=sfoster Differential Revision: https://phabricator.services.mozilla.com/D3846

Bug 1369941 - Provide more advice about how to write fuzzy() annotations on reftests. r=dholbert Differential Revision: https://phabricator.services.mozilla.com/D3940

Bug 1369941 - Remove ability to specify fuzzy()/fuzzy-if() in reftest manifests without ranges. r=dholbert I'm removing this no-longer-used feature because it promotes a behavior (using the default 0 minimum) that means we never see reports of unexpected passes when the bugs are fixed, and thus aren't protected from the bugs regressing again. Differential Revision: https://phabricator.services.mozilla.com/D3566

Bug 1484113 - part 1: Create HTMLEditor::GetFirstTableRowElement() for internal use of nsITableEditor::GetFirstRow() r=m_kato nsITableEditor::GetFirstRow() is an XPCOM method, so, for internal use, we should create non-virtual method, that is GetFirstTableRowElement(). This patch makes it never return NS_SUCCESS_EDITOR_ELEMENT_NOT_FOUND since nobody refers it and it's detectable. If the method returns nullptr without error, it's the case of NS_SUCCESS_EDITOR_ELEMENT_NOT_FOUND. Additionally, this patch changes the return type of GetFirstRow() from Node to Element since it always return an Element node if not null. Differential Revision: https://phabricator.services.mozilla.com/D3780

Bug 1484113 - part 0: Create automated tests for nsITableEditor::GetFirstRow() r=m_kato Differential Revision: https://phabricator.services.mozilla.com/D3779

Bug 1476914 - Add fuzzy-if on Bug 1443902's reftests for Android. r=masayuki Android's reftest of Bug 1443902 is failed rarely (Bug 1476914, Bug 1475049 Bug 1477502 and Bug 1476129) due to "image comparison, max difference: 1, number of differing pixels: 1". But I don't know why difference is 1 and I think that this might be reftest framework for Android or Android emulator issue. So I would like to add fuzzy-if as workaround. Differential Revision: https://phabricator.services.mozilla.com/D3859

Bug 1485133 - Remove Web Animation polyfill in video controls r=birtles Differential Revision: https://phabricator.services.mozilla.com/D3918

Merge mozilla-inbound to mozilla-central. a=merge

Bug 1484888 - Apply upstream patch that fixes a clang crash with stack overflow on PGO + LTO on Linux. r=froydnj For some reason, clang 6 crashes with a stack overflow on PGO + LTO on Linux 64 bits. Clang 7 doesn't, but has other problems. After some bisecting, I found the following: - r322684 is the first revision that is broken on the release_60 branch. - that revision is a cherry pick of r322313 from trunk, which is similarly broken. - trunk was fixed by r322325, which, funnily enough, predates when r322313 was cherry-picked. While the change from r322325 is relatively large, mixing multiple different changes in a single commit, there also haven't been significant changes to the same file on trunk since (one macro name change, one documentation change, and a change related to debug info), which would tend to indicate the change is not going to break anything, or at least not more than upgrading to clang 7 would. The exact part that fixes the issue could probably be found in this large commit, but I didn't feel like digging into it further considering the above.

Bug 1484944 - Remove nsSHEnumerator. r=qdot

Bug 1470914 - land NSS d3f512d4f76e UPGRADE_NSS_RELEASE, r=me

Bug 1482457 - Update expectations for ignore-opens-during-unload to account for crashes on macOS and Windows debug. CLOSED TREE

Bug 1471339 - Add RUSTFLAGS to Linux coverage build to enable gcov profiling for Rust. r=jmaher

Bug 1484852 - Update svg/text/reftests to account for passes on Windows. CLOSED TREE

Backed out 3 changesets (bug 1475417) for failing docker configuration ona CLOSED TREE Backed out changeset 972ad5dc9a84 (bug 1475417) Backed out changeset 13020b58f0fa (bug 1475417) Backed out changeset 50ed38c98cc0 (bug 1475417)