Bug 1238137 - Define a telemetry histogram for tracking the input methods used to trigger scrolling. r=kats

Bug 1248822 - In LayerManagerComposite::UpdateAndRender(), call PostProcessLayers() before LayerTreeInvalidation. r=mattwoodrow The reason is that PostProcessLayers() can change the effective visible region, and LayerTreeInvalidation needs the final effective visible region. MozReview-Commit-ID: 1wLROyOTcIB

Bug 1238656 - Part 3: bypass cache for homescreen icons r=mcomella MozReview-Commit-ID: Bvf6GyWXqQn

Bug 1238656 - Part 2: introduce FLAG_BYPASS_CACHE_WHEN_DOWNLOADING_ICONS to avoid icon downscaling r=mcomella MozReview-Commit-ID: BXLqJ9wjzf7

Bug 1238656 - Part 1: move best icon size selection into its own method r=mcomella MozReview-Commit-ID: AWw50DDoLcL

Bug 1227730 - Support closing libnotify alerts. r?karlt MozReview-Commit-ID: LR3OiP0miEm

Bug 1166365 - Add tests narrator tests. MozReview-Commit-ID: NKo8xwiKzK

Bug 1166365 - Introduce Narrate extension. r?Gijs MozReview-Commit-ID: 6tJIu7C4eAv

Bug 1166365 - Add some padding around paragraphs for nice highlighting. r=Gijs MozReview-Commit-ID: 6LEDaLRmFmL

Bug 1166365 - Pass window object in notification. r?Gijs MozReview-Commit-ID: GNo1fAQFif8

Bug 1166365 - Pluralize dropdown logic. r=Gijs r?margaret MozReview-Commit-ID: KCayCX4r8xQ

Bug 1248799 - Don't call method on potentially null tab Object. r=sebastian MozReview-Commit-ID: 8SkJx0DsRWD

Bug 1248450: Send the graphics messages to the parent process. r=dvander MozReview-Commit-ID: EshCrdT5lYu

Bug 1244650 - Failure to clear Forms and Search Data on exit. r=yoric The problem is due to sanitization happening too late in the shutdown cycle. The Sanitizer depends on Places shutdown, that recently moved to async shutdown. That change caused shutdown to happen completely at profile-before-change, unfortunately during that phase it's impossible to predict which services are already shutdown. The patch restores the previous Places shutdown procedure, thus clients are notified earlier, during profile-change-teardown. Additional meaningful changes: * Fixes FX_SANITIZE_TOTAL telemetry to properly count total time taken by sanitize. * Makes each cleanup operation isolated from other errors to try cleaning up as most as possible. * In case of multiple sanitization sub steps, each step is isolated by a try/catch, the last seen exception is reported upstream. * Makes FX_SANITIZE_HISTORY actually measure history, not other random stuff. * Removes TOPIC_SIMULATE_PLACES_MUST_CLOSE_1 since we can now just use profile-change-teardown for shutdown phase 1. MozReview-Commit-ID: HroLvbi25IC

Bug 1245916: Turn on no-undef in toolkit/mozapps/extensions. r=rhelmer Mostly just declaring globals that Cu.imports defines but there are some actual bugs here that have been fixed as well as one test that just never ran because of a hidden exception. MozReview-Commit-ID: J6uIpYp8ANx

Bug 1245916: Import more head files for xpcshell tests. r=pbrosset xpcshell tests used to use head_*.js files so this adds those for global discovery. MozReview-Commit-ID: BOsoGIpwdgu

Bug 1245916: Add additional default globals. r=felipe This defines a few additional globals but also turns on the browser environment for everything in browser and toolkit. This may lead to some false negatives but we have lots of code that runs in a browser context so in the name of getting rules turned on I think this is a useful step. MozReview-Commit-ID: BdWouZGK6d

Bug 1245916: Add additional browser window scripts to eslint globals. r=felipe This adds more of the scripts that browser.js relies on and also makes browser-chrome head files import the browser.js globals. The MOZ_JSDOWNLOADS block in contentAreaUtils only seems to hide a single function, I don't see any need to keep hiding that now we're on by default. MozReview-Commit-ID: 5zvF3JtJrZG

Bug 1245916: XBL bindings should support global declarations in comments. r=miker To properly lint XBL files we need to support things like import-globals-from and other ESlint comment directives so we have to pass comments through to the code blocks that ESlint parses. Unfortunately the way the XBL processor works now is by passing a separate code block for every method/property/etc. in the XBL and ESlint doesn't retain state across the blocks so we would have to prefix every block with every comment. Instead this change makes us output just a single block that roughly looks like this: <comments> var bindings = { "<binding-id>": { <binding-part-name>: function() { ... } } } This has some interesting bonuses. Defining the same ID twice will cause a lint failure. Same for the same field in a binding. The line mapping is a little harder and there are still a few lines that won't map directly back to the original file but they should be rare cases. The only downside is that since some bindings have the same binding declared differently for different platforms we have to exclude those from linting for now. MozReview-Commit-ID: CAsPt5dtf6T

Bug 1245916: Unify eslint global discovery rules. r=pbrosset While working on turning on no-undef I discovered that the various rules we have for defining globals are a little inconsistent in whether the files they load recurse through import-globals-from directives and none of them imported eslint globals directives. I think we're better off putting all this global parsing code in a single place rather than spread across multiple rules. Have one rule to turn it on for parsed files and one function to load globals from other files and make them share most of the code so we won't get inconsistent. If we find us needing to turn on/off individual features we can figure out a way to do that in the future. This patch does that, the globals.js file does all global parsing with a shared object that receives events from the AST, either through from an ESlint rule or from a simple AST walker using estraverse. MozReview-Commit-ID: 9KQZwsNNOUl