Bug 1396182 - Wait for the styleditor animations to be done before running tests; r=ochameau MozReview-Commit-ID: 2QiW1E5RroI

Bug 1399390 - Use lazy-require in Netmonitor's webpack.config; r=jdescottes MozReview-Commit-ID: Lt07vlWXLeg

No bug - Revendor rust dependencies

servo: Merge #18495 - Measure PropertyDeclaration more thoroughly (from nnethercote:derive-PropertyDeclaration); r=jdm This patch replaces the handwritten MallocSizeOf implementation for PropertyDeclaration with a derived one, which gives much more thorough measurement. This requires (a) deriving MallocSizeOf for a *lot* of additional types (most of which already have `derive(HeapSizeOf)` in Servo builds), and (b) implementing MallocSizeOf for a few more types in the `malloc_size_of` crate. These changes would significantly improve the reporting coverage for gmail if it weren't for the fact that SpecifiedUrl isn't measured due to a lack of clarity about its fields; that can be fixed as a follow-up once bug 1397971 has landed. <!-- Please describe your changes on the following line: --> --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [ ] These changes fix #__ (github issue number if applicable). <!-- Either: --> - [ ] There are tests for these changes OR - [X] These changes do not require tests because testing is on the Gecko side. <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: 097cea240fe9b1d96fa4ef5ffa984f09e0bd04f3

Bug 1398811 - Document the edge cases for the 'update' ping. r=chutten This additionally adds the edge cases that were found in bug 1397322 and bug 1397765. MozReview-Commit-ID: 7CFEgePpOK1

Bug 1395834 - Implement theme loader; r=nchevobbe MozReview-Commit-ID: 5AR0AX5tTnB

Bug 1395834 - Launchpad is broken; r=nchevobbe MozReview-Commit-ID: CdeEvvE6ExB

Bug 1399651 - Don't run the library animations in popup windows with toolbar=false. r=Gijs MozReview-Commit-ID: 2vswZ2BTFwp

Bug 1399392 - Don't hardcode .config, use XDG_* environment vars. r=jld MozReview-Commit-ID: 30j9VbHUjFn

Bug 1363378 - Set close-on-exec in sandbox-related sockets held by parent process. r=gcp If these aren't close-on-exec, they can be inherited by the crash reporter process after the parent process has crashed and exited, causing child processes to continue running when the IPC I/O thread blocks in the file broker trying to open a GeckoChildCrash temp file. (Empirically, the main thread then blocks waiting for the I/O thread.) Operations that run on dedicated threads, like playing media, may continue even though the main and IPC threads are locked up, resulting in videos that keep playing sound even though the browser seems to no longer exist. If the broker socket is closed as expected when the parent process exits, the child will return failure from the brokered file operation and then go on to get an IPC error due to the parent process's nonexistence, and will exit as normal. This patch makes the same change to rejected syscall reporting, even though that's a one-way asynchronous message with no response to wait for, just in case something goes wrong enough to fill the entire socket buffer but not so badly broken that it would wind up in an infinite loop anyway. SOCK_CLOEXEC has been present since Linux 2.6.26, and it would be used only if seccomp-bpf is available, so it should be safe to use unconditionally. MozReview-Commit-ID: 7tDPBJILzlj

Bug 1399393 Refactor create_tasks to avoid bottlenecks r=dustin MozReview-Commit-ID: cJW5X3HSCx

Bug 1369361 - Backport SQLite fix removing rand_s() in an attempt to avoid Lenovo DLL crashes. r=mak SQLite check-in 3a2793aa: https://www.sqlite.org/src/info/3a2793aa65727cbb MozReview-Commit-ID: 1Q4tGhWLoRu

servo: Merge #18496 - do a second pass on the style sharing cache after computing the rule node (from bholley:2ndpass); r=emilio https://bugzilla.mozilla.org/show_bug.cgi?id=1397976 Source-Repo: https://github.com/servo/servo Source-Revision: 298b1363ffd7e830a6ad28424421ead6628ac9b7

Bug 1398656 - Always build the form autofill system add-on but disable it by default on release. r=lchang The pref will gradually be flipped via Shield to "detect" on release. MozReview-Commit-ID: LaiEub8v05t

Bug 1393437 - Add a checkbox to preferences to control whether the separate Search Bar is present in the toolbar. r?Gijs ui-review=epang MozReview-Commit-ID: 8gpukk8BhxG

Bug 1307929 - Photon updates for new webconsole UI; r=honza, gl. This patch does not change the color for Reps, which is done in Github and will be available in the 0.0.13 Reps bundle. MozReview-Commit-ID: ANNjYc2zW3j

Bug 1387594 - Sprinkle -moz-font-smoothing-background-color declarations over the CSS. r?dao There's only one interesting case here: the active tab. When rendering the label of an overflowing active tab into the fadeout mask surface, text rendering must not use the font smoothing background color for dark vibrancy. Instead, it needs to use the color of the tab itself for best results. Alternatively, we could set the font smoothing background color of the active tab to "transparent", because this text is not on top of a vibrant background. However, doing so would lose the subpixel AA and would not look as crisp. MozReview-Commit-ID: 28MKCz1vmb9

Bug 1387594 - Add system colors for use in conjunction with -moz-font-smoothing-background-color and vibrant -moz-appearances. r?dbaron MozReview-Commit-ID: IxXZwONxy41

Bug 1387594 - Respect the font smoothing background color in pushed layers again. This backs out bug 1386643. r?jrmuizel MozReview-Commit-ID: KNsd7tKuRk1

Bug 1387594 - Set the font smoothing background color based on the -moz-font-smoothing-background-color property. r?mattwoodrow MozReview-Commit-ID: B3PVIvMswf8