Bug 1431337 - Skip hidpi test of startup images because they overflow in Linux MozReview-Commit-ID: Ldu9evdGiWf

Bug 1431337 - Scale content for the actual monitor, not the first one; r?stransky We need to use scaling factor of the monitor on which application is actually positioned. Previously we used ScreenHelperGTK::GetGTKMonitorScaleFactor() which use the first monitor. This does not work on hidpi+normal dpi monitors setup. The GetSystemFontInfo() cannot return scaled value of the font by default monitor scale factor. We need to scale it in nsLookAndFeel::GetFontImpl by aDevPixPerCSSPixel like implementation for Windows does. We also need to check layout.css.devPixelsPerPx because we cannot scale per monitor when this preference is set to positive number. MozReview-Commit-ID: AwT2NvkEqvz

Bug 1435733 - Upgrade mixed display content pref. r?mayhemer,baku,francois MozReview-Commit-ID: ETIgVF3zhRu

Bug 1430841 Re-enable the Reduce Timer Precision pref for CSS Animations tests r?birtles Currently CSS Animations are exempted from Reduce Timer Precision, so this isn't needed. Additionally, when we test by overriding that restriction, these tests aren't run, which leads to confusion. MozReview-Commit-ID: Gv6T3oGO475

Bug 1430841 Eliminate float fuzziness in ReduceTimerPrecision r?froydnj We eliminate float fuzziness by calculating the reduced precision using integers in microseconds. (This means we automatically lose any granularity about nanoseconds, but that's okay.) MozReview-Commit-ID: D9ReLknsafo

Bug 1430841 Refactor ReduceTimePrecision and add (failing) gtests This commit adds a gtest calling ReduceTimePrecision that illustrates several failing test cases from float fuzziness, as well as generating a ton of test cases at random that also fail. MozReview-Commit-ID: Epia5gm5Ahb

Bug 1438953 Increase the epsilon on timer reduction tests r?froydnj In Javascript, we re-clamp timers to ensure they stay the same. Because of double imprecision sometimes they don't stay the same, and are clamped downwards. If that happens we detect it, and if we were originally off by an epsilon from a clamped value, we accept the value in the name of double imprecision. However, the epsilons were originally chosen somewhat arbitrarily. They worked for small numbers, where imprecision from doubles were very small. But large doubles have much less precise fractional parts. So the epsilons were too small for large numbers where the imprecision was larger. MozReview-Commit-ID: HnYYo4cuv96

Bug 1438482 - logErrorInPage should produce an error log; r=bgrins MozReview-Commit-ID: Ly9kDNwGthG

Bug 1399242 - Do not render if the Net panel isn't currently selected; r=ochameau MozReview-Commit-ID: KdXkyt49upL

Bug 1439358 - Part 7 - Change how visibility is controlled so knownViews can be removed. r=Gijs MozReview-Commit-ID: 9dVZ1cOto8O

Bug 1439358 - Part 6 - Close the main view synchronously before opening it in a different panel. r=Gijs MozReview-Commit-ID: FciQH815F95

Bug 1439358 - Part 5 - Decouple view events from view visibility. r=Gijs This stops redundant ViewHiding and late ViewShown events from being dispatched when the panel is closed during a ViewShowing event or a transition, and stops dispatching ViewHiding events when a view becomes invisible but is still open. The panelMultiView property on "panelview" nodes is now set to null when the view is closed, indicating that the view can be immediately reused in a different panel. The Places view had to be updated so it doesn't rely on this property during the PanelMultiViewHidden event. MozReview-Commit-ID: B1yU6si3eD3

Bug 1439358 - Part 4 - Handle panel hiding during ViewShowing events. r=Gijs The logic that is specific to each of the showMainView, showSubView, and goBack functions has been moved into them, leaving an _openView helper in place of the complex _showView function. This makes it easier to add additional logic like the one in showSubView handling the common case where the panel is hidden during a ViewShowing event. MozReview-Commit-ID: 5WvW6THWbyb

Bug 1439358 - Part 3 - Open views before the transition and close them after it. r=Gijs MozReview-Commit-ID: 1VoIImxVTDN

Bug 1439358 - Part 2 - Always raise ViewShowing events and don't update the "current" property. r=Gijs The ViewShowing event is now called earlier and unconditionally, since we don't set the "current" attribute and call showMainView while the panel is closing anymore. It is already the case that the ViewShowing event handlers don't depend on the "current" property, so we don't need to keep track of it before ViewShown events are dispatched. MozReview-Commit-ID: Ii4SN03KjwW

Bug 1439358 - Part 1 - Support "panelview" elements located anywhere in the document. r=Gijs The showSubView public method now aligns with its callers and doesn't return a Promise anymore. The showMainView method still returns a Promise because at the moment it is used externally for asynchronous cleanup. MozReview-Commit-ID: FcnEx5f5HKh

Bug 1438892 - Update bindings for API change in WR PR 2435. r?jrmuizel MozReview-Commit-ID: EVw2PhfDAmf

Bug 1438892 - Update reftest results for changes from WR PR 2423. r?jrmuizel MozReview-Commit-ID: LAqklCRsg8Y

Bug 1438892 - Update annotations from WR PR 2426. r?jrmuizel MozReview-Commit-ID: 5o3YCJKxlje

Bug 1438892 - Update reftest fuzziness for WR PR 2405. r?jrmuizel MozReview-Commit-ID: HcOke96a4Z2