Bug 1379021 - Remove card wrapper from highlight items. r?mcomella MozReview-Commit-ID: 3CYSz6aTxqm

Bug 830415 - Part 2 - Move the front-end code that stores download metadata in history to the DownloadHistory module. r=mak Regression tests will be added in bug 1381411 when methods to retrieve the metadata will be available. MozReview-Commit-ID: I3MgwM0EOty

Bug 830415 - Part 1 - Update the header styles of the Downloads API modules. r=mak File comments now consistently provide an overview instead of repeating the object comments. Redundant headers are removed together with other style changes, and mode lines are removed as they are only used by a small fraction of the JSM files in the tree. MozReview-Commit-ID: 42fs7rT2BNM

Bug 1384181 - Add utility dump functions for debugging. r?jrmuizel MozReview-Commit-ID: IRY8RsYqUkB

Bug 1384181 - Build WebRenderLayerScrollData instances for remote layer trees. r?jrmuizel This adds handling for nsDisplayRemote frames, so that we create a WebRenderLayerScrollData item for each nsDisplayRemote frame that we encounter. This is the equivalent of a "ref layer" in a normal layer tree, and allows the APZ side to glue together the scroll data from different processes into a full tree. MozReview-Commit-ID: DXuWR2w90kg

Bug 1384181 - Ensure that the WebRenderScrollData has a single root layer node. r?jrmuizel The semantics of the WebRenderScrollData structure is that the per-layer structures form a tree with a single root node. When we build the data structure from the display list, we are generating (for now) a flat list. Therefore we need to synthesize a root node in order to make stuff work as intended. MozReview-Commit-ID: 5vNOyKSQoj8

Bug 1384181 - Reorganize the WebRenderScrollData code to work with layers-free transactions. r?jrmuizel Until now WebRenderScrollData was only used with "layers" WR transactions, but we want to use it with layers-free transactions as well. As such, we need to allow collecting information from display items instead of layers. This restructures the code a little bit to allow that. This patch should not have any functional effect on the "layers" codepath, but on the "layers-free" codepath it is now actually populating some rudimentary data into the WebRenderScrollData before sending it across. This will be fleshed out in future patches. MozReview-Commit-ID: CMgwUzcihAk

Bug 1383257 - Schedule windows nightlies via cron. r=kmoir a=Tomcat for: Land changes to flip windows nightlies on, and to tier 1 on central MozReview-Commit-ID: 62cpCHbYN5Y

Bug 1359076: Disable all Device Sensor APIs except orientation by default r?bkelly This patch disables device sensors except orientation by default. It implements per-sensor prefs to disable orientation, proximity and ambient light selectively. The patch also makes the pref checks happen at runtime (versus on process start) using Preferences::AddBoolVarCache. MozReview-Commit-ID: EA8ARjjtlkF

Bug 1384584 - TextComposition::DispatchCompositionEvent() shouldn't send composition events to focused TabParent after its RequestIMEToCommitComposition() synthesizes eCompositionCommit(AsIs) event synchronously r?m_kato When TextComposition::RequestIMEToCommitComposition() is called but the request is handled by native IME asynchronously, TextComposition synthesizes eCompositionCommit(AsIs) event to commit composition synchronously. (This behavior helps web apps which tries to commit composition from JS.) Then, TextComposition::DispatchCompositionEvent() should ignore following composition events which are actually sent from native IME. However, if composition is in a remote process, TextComposition::DispatchCompositionEvent() in the main process doesn't discard the following events coming from native IME. Therefore, ContentCacheInParent is confused by this unexpected events. So, TextComposition::DispatchCompositionEvent() shouldn't send the following unnecessary composition events to TabParent. Note that in remote process, composition is committed synchronously with the hack mentioned above and synthesized eCompositionCommit(AsIs) event of TextComposition::RequestIMEToCommitComposition() in the parent process looks like coming from native IME. Therefore, following composition events coming from native IME are not necessary for the remote process. MozReview-Commit-ID: 2uKFxcAq88J

Bug 1384517 - Generate Marionette server API docs; r?automatedtester This is automatically generated from `./mach marionette doc`. MozReview-Commit-ID: JpCfM1LGUnh

Bug 1384517 - Exclude testing/marionette/doc from linting; r?automatedtester It also lists directories instead of globbing all files. MozReview-Commit-ID: ApxmKVfEWTz

Bug 1384517 - Add "marionette doc" subcommand to generate docs; r?automatedtester This patch introduces a new top-level mach command "marionette" that can be invoked as `./mach marionette`. It offers two subcommands, "test" and "doc". The "test" subcommand is functionally equivalent to the existing "marionette-test" command, which this patch deprecates. The "doc" subcommand generates the Marionette server API documentation using jsdoc, which it is presumed is already installed on the system. A future patch will make this subcommand more sophisticated, but this should work for now. It also comes with an --http <host>:<port> flag which spins up an HTTPD serving the documentation. MozReview-Commit-ID: DAoHC8tHJQF

Bug 1384517 - Fix testing/marionette API docs; r?automatedtester Various fixes to make the generated API documentation from testing/marionette somewhat easier to read. MozReview-Commit-ID: F9duuQoOYBt

Bug 1384517 - Provide jsdoc rules for testing/marionette; r?automatedtester MozReview-Commit-ID: HVzcmR767j8

Bug 1384517 - Render Marionette README as HTML; r?automatedtester To include the Marionette server README in the generated API documentation, we need to provide some semantic rules describing the document structure. searchfox.com will soon also be able to render HTML documents inline, making it possible to browse testing/marionette/README.html directly from the source browser. MozReview-Commit-ID: Bc452RC1k6j

Bug 1383257 - DO NOT LAND - changes applied only to date branch MozReview-Commit-ID: 7SL5RZv4Y3X

Bug 1383257 - Schedule windows nightlies via cron. r=kmoir for: Land changes to flip windows nightlies on, and to tier 1 on central MozReview-Commit-ID: 62cpCHbYN5Y

Bug 1383257 - Do not attempt to schedule win10 hardware testing, unless we're on try. r=grenade for: Land changes to flip windows nightlies on, and to tier 1 on central MozReview-Commit-ID: EB0UVV3zQYX

Bug 1383257 - Flip windows testing to be tier 1 by default. r=kmoir for: Land changes to flip windows nightlies on, and to tier 1 on central MozReview-Commit-ID: Ecqd48ef01i