Bug 1388738 - reuse devtools-startup initDevTools in DevToolsShim MozReview-Commit-ID: 7Qr06CZBYuf

Bug 1388454 - remove access to the com.apple.pasteboard.1 mach service from content processes; r?haik MozReview-Commit-ID: EXb6UDYohZT

Bug 1363922 - Part 1: Remember about the DisplayListBuilder during BuildDisplayList for so GetScrolledRect can use its reference frame cache. r=kats MozReview-Commit-ID: DDU1Zi0cFOe

Bug 1387399 - Part 2: SIMD optimize ScaleToOuterPixels. r=jrmuizel MozReview-Commit-ID: C667VsdFibx

Bug 1387399: Add SIMD optimizations for methods commonly used in nsRect. r=jrmuizel MozReview-Commit-ID: 4dakIQ3S0FX

Bug 1388588: Only zoom absolute lengths. r?Manishearth As silly as it may seem to specify font-sizes using viewport units, we weren't handling zoom for them correctly either. MozReview-Commit-ID: 3Q6phYAu5CE

Bug 1381071: Cache styles on display: none subtrees. r?heycam MozReview-Commit-ID: DeTYlPYfjSV

Bug 1385003 - Add missing call to deinit the renderer before dropping it. r?kvark MozReview-Commit-ID: 3dmttqFqMJE

Bug 1385003 - Update webrender bindings for API change in WR cset c7a5b78d. r?nical MozReview-Commit-ID: DY5vwlv4JYM

Bug 1385003 - Update webrender bindings for API changes in WR cset 55acc967. r?nical MozReview-Commit-ID: 3pW2ssFdb50

Bug 1385003 - Mark counter-style-rule-clone as failing from WR cset 921bde2. r?jrmuizel This was already marked fuzzy but now the difference between the test and reference images is even more pronounced. Technically this might still be fuzzable because the thickness of the text (which is what is different) is not what the test is testing for. But if we fuzz it the fuzz numbers would be so high that legitimate failures might get fuzzed as well, so it's better to just mark it failing for now and deal with it later. MozReview-Commit-ID: 3Wt32XB1TWG

Bug 1385003 - Autogenerated changes to go with webrender update. r?jrmuizel This regenerates the cargo lockfiles and FFI bindings header. It also revendors the third_party/rust libraries. MozReview-Commit-ID: ID0YhoIH6cz

Bug 1385003 - Use a different WebRenderAPI instance for each WebRenderBridgeParent. r=kats Previously, the WebRenderBridgeParent for each content layer tree would use the same WebRenderAPI instance as the top-level WebRenderBridgeParent for that window. However, in order to make the namespacing changes work we now need to use a separate WebRenderAPI instance for each WebRenderBridgeParent. The content WebRenderAPIs are cloned from the parent one, so that they all share the same backend, but can allocate resource IDs in distinct namespaces. MozReview-Commit-ID: 7VTFL8F09n7

Bug 1385003 - Drop the hacky gecko IdNamespace allocator and use the IdNamespace from WR to avoid mismatches. r?sotaro MozReview-Commit-ID: 410h1ZkWBGL

Bug 1385003 - Update webrender bindings for API changes in WR cset f6d81d9. r?kvark In theory the upstream API change should allow us to share the same WR renderer instance across multiple WebRenderAPI instances. For now however I retain the existing behaviour of one WR instance for each WebRenderAPI instance, but keep track of the document id in a new DocumentHandle struct. The C++ side keeps a pointer to this DocumentHandle struct instead of the raw RenderApi. MozReview-Commit-ID: I9pCKOY1OYx

Bug 1385003 - Update webrender to commit e68c8acb021656440d26ac46e705e7ceb31891e6. r?jrmuizel MozReview-Commit-ID: Kw49PJqoLn4

Bug 1388746 - Do not split start/end text nodes in deleteContents/extractContents; r?smaug If a range endpoint is in the middle of a text node, and you call deleteContents() or extractContents(), the spec says to delete the data from the node. In the case of extractContents(), the inserted text node is a clone with its data set to the bit that was deleted. <https://dom.spec.whatwg.org/#dom-range-deletecontents> <https://dom.spec.whatwg.org/#dom-range-extractcontents> We don't do this. Instead, we split the text node. Then the bit to delete is deleted naturally at a later stage together with all the other nodes. The result is the same, but on the way there we do a bunch more node mutations. This causes extra mutation records, which cause us to fail a WPT test. Chrome passes. Changing to match the spec actually reduces our lines of code anyway. MozReview-Commit-ID: FTTV5yNSj71

Bug 1384482 - Rename android-api-15 into android-api-16 MozReview-Commit-ID: 4j66pTZEJzq

Bug 1381556 - adjust panel widths to accommodate longer/wider content, r?mikedeboer MozReview-Commit-ID: 6bOoRIfttEy

Bug 1388695 - Show the payload for non main ping in about:telemetry r?gfritzsche Add a raw payload section when looking at a non main ping. MozReview-Commit-ID: 2dU8apRfzLP