Bug 1345932 - show warning info in about:debugging#workers if multi-e10s is on;r=ochameau If multi e10s is enabled, service worker debugging is unavailable. We temporarily disabled the start/push/debug buttons in about:debugging for all service workers if multi-e10s is on. A warning section is also displayed on top of about:debugging, letting the user know that they can set dom.ipc.processCount to 1 in order to force a single content process and restore debugging capabilities. MozReview-Commit-ID: IPAlbOq2Hij

Bug 1345932 - show warning info in about:debugging#workers if multi-e10s is on;r=ochameau If multi e10s is enabled, service worker debugging is unavailable. We temporarily disabled the start/push/debug buttons in about:debugging for all service workers if multi-e10s is on. A warning section is also displayed on top of about:debugging, letting the user know that they can set dom.ipc.processCount to 1 in order to force a single content process and restore debugging capabilities. MozReview-Commit-ID: IPAlbOq2Hij

Bug 1342928 - Keep the commands / buttons state in sync; r=jwalker This was a regression given by bug 1320149; in order to keep the performance gain I created a lightweight object (`CommandState`) that is required from both gcli's command and toolbox so that the last one doesn't need to be strong coupled with the first one. Also fixing an inconsistency of buttons' state when we enter/exit in/from RDM. MozReview-Commit-ID: 3NcTt6i4ezx

Bug 1345932 - show warning info in about:debugging#workers if multi-e10s is on;r=ochameau If multi e10s is enabled, service worker debugging is unavailable. We temporarily disabled the start/push/debug buttons in about:debugging for all service workers if multi-e10s is on. A warning section is also displayed on top of about:debugging, letting the user know that they can set dom.ipc.processCount to 1 in order to force a single content process and restore debugging capabilities. MozReview-Commit-ID: IPAlbOq2Hij

Bug 1320744 - Part 3, implement nsIThreadRetargetableRequest in HttpChannelChild. r=mayhemer MozReview-Commit-ID: FyLXlkQde3h

Bug 1320744 - Part 2, Allow ChannelEventQueue to perform flush on multiple threads. r=mayhemer MozReview-Commit-ID: Egu2mvwFTUF

Bug 1320744 - Part 1, make refcounter of HttpChannelChild thread-safe. r=mayhemer MozReview-Commit-ID: 5Br1WLlpvcR

Bug 1345932 - show warning info in about:debugging#workers if multi-e10s is on;r=ochameau If multi e10s is enabled, service worker debugging is unavailable. We temporarily disabled the start/push/debug buttons in about:debugging for all service workers if multi-e10s is on. A warning section is also displayed on top of about:debugging, letting the user know that they can set dom.ipc.processCount to 1 in order to force a single content process and restore debugging capabilities. MozReview-Commit-ID: IPAlbOq2Hij

Bug 1347892 part 2 - don't pass incomplete visibility states into decoder; r?jwwang It's possible that a IN-TREE media element's NotifyOwnerDocumentActivityChanged() has been called but OnVisibilityChange() haven't. At that moment, we don't have full visibility states, so don't bother to pass incomplete information into media decoder. MozReview-Commit-ID: JPQsimGXsjA

Bug 1347892 part 1 - initialize a media element's mVisibilityState to be UNTRACKED; r?jwwang MozReview-Commit-ID: Bkkh6hvCNu4

Bug 1224225: Tests for punycode/unicode in CSP source matching code r?ckerscb MozReview-Commit-ID: 21Mr9ekUvnk

Bug 1224225: Use GetAsciiHost in CSP source matching code r?ckerschb MozReview-Commit-ID: B7SwUEMiVwc

Bug 1317783 - Put PushApk tasks in-tree MozReview-Commit-ID: 8uGIuj7OXwZ

Bug 1347884 - Enable eslint cyclomatic complexity rule at existing levels. r?jaws Enable the rule with the maximums set to avoid current failures, except for test_form_autocomplete which is very high (82). The levels are set per major area, with existing warnings being changed to errors. MozReview-Commit-ID: 37M6Ry0Mr1c

Bug 1217238 - Reduce time precision when javascript.options.privacy.reduce_time_precision is on. r=bz This patch was adapted from Tor bug 1517. To offer some protection against timing attacks by JS content pages, in this patch we round the various time-exposing APIs (such as Date and Event.timeStamps) to the nearest 100 ms when the pref "javascript.options. privacy.reduce_time_precision" is on. When we're in worker threads, we get the pref from the WorkerPrivate object. MozReview-Commit-ID: eGucM9nGTn

Bug 1217238 - Propagate changes of javascript.options.reduce_time_precision to workers. r=bz This pref is created for the next patch. Because we need to get this pref in workers, I added this pref to WorkerPrefs.h so RuntimeService will broadcast pref changes for us, and update all the workers recursively. This pref is also added to the js context options because the Date API needs it. MozReview-Commit-ID: JOkOR2Wek5C

Bug 1217238 - Regression tests for reducing precision of time exposed by Javascript. r=bz This patch is adapted from Tor bug 1517. Test that the following javascript codes will return timeStamps that are rounded to 100ms. performance.now() new Date().getTime() new Event("").timeStamp new File([], "").lastModified new File([], "").lastModifiedDate.getTime() audioContext.currentTime * 1000 canvasStream.currentTime * 1000 video.currentTime * 1000 audio.currentTime * 1000 The first five codes are also tested in simple workers and nested workers, created before and after the pref is on, to ensure that the pref has correctly propagated. MozReview-Commit-ID: CuoxmGRrBnm

Bug 1341739 - Stylo: Add support for :valid/:invalid/:-moz-ui-valid pseudo-classes r?xidorn MozReview-Commit-ID: K3WSun7UGFo

Bug 1347673 - Adjust layout accordingly for later enabled controls. r=jaws MozReview-Commit-ID: Lj7kttJ9skU

Bug 1299406 - [mortar][PDF] Implement document outlines. r=evelyn MozReview-Commit-ID: 2Evg13Ohwg