12282fc61f3e7a08c20157bbff91a0dca5083fbb: Bug 1431337 - Skip hidpi test of startup images because they overflow in Linux draft
Jan Horak <jhorak@redhat.com> - Tue, 20 Feb 2018 11:13:04 +0100 - rev 757270
Push 99731 by bmo:jhorak@redhat.com at Tue, 20 Feb 2018 15:10:49 +0000
Bug 1431337 - Skip hidpi test of startup images because they overflow in Linux MozReview-Commit-ID: Ldu9evdGiWf
3b70fc9f3a811e231573ebd64117af56ab20ac96: Bug 1431337 - Scale content for the actual monitor, not the first one; r?stransky draft
Jan Horak <jhorak@redhat.com> - Thu, 18 Jan 2018 11:52:59 +0100 - rev 757269
Push 99731 by bmo:jhorak@redhat.com at Tue, 20 Feb 2018 15:10:49 +0000
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
52735f869dc7283b780706446bda440fbef03000: Bug 1435733 - Upgrade mixed display content pref. r?mayhemer,baku,francois draft
Jonathan Kingston <jkt@mozilla.com> - Mon, 05 Feb 2018 15:37:27 +0000 - rev 757268
Push 99730 by bmo:jkt@mozilla.com at Tue, 20 Feb 2018 15:01:38 +0000
Bug 1435733 - Upgrade mixed display content pref. r?mayhemer,baku,francois MozReview-Commit-ID: ETIgVF3zhRu
85af55e5c3b573c8d192de2a014a7762fa85bf58: Bug 1430841 Re-enable the Reduce Timer Precision pref for CSS Animations tests r?birtles draft
Tom Ritter <tom@mozilla.com> - Fri, 16 Feb 2018 15:45:33 -0600 - rev 757267
Push 99729 by bmo:tom@mozilla.com at Tue, 20 Feb 2018 14:53:30 +0000
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
7f4edb93d9d22d95e3243770142b51ceb2ab670d: Bug 1430841 Eliminate float fuzziness in ReduceTimerPrecision r?froydnj draft
Tom Ritter <tom@mozilla.com> - Mon, 12 Feb 2018 16:17:03 -0600 - rev 757266
Push 99729 by bmo:tom@mozilla.com at Tue, 20 Feb 2018 14:53:30 +0000
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
57f3d3547736c7572aa6c0b0a91a167bd520803e: Bug 1430841 Refactor ReduceTimePrecision and add (failing) gtests draft
Tom Ritter <tom@mozilla.com> - Mon, 12 Feb 2018 13:11:18 -0600 - rev 757265
Push 99729 by bmo:tom@mozilla.com at Tue, 20 Feb 2018 14:53:30 +0000
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
601e7e68ee4e8b03453a05fc325163952b850cf2: Bug 1438953 Increase the epsilon on timer reduction tests r?froydnj draft
Tom Ritter <tom@mozilla.com> - Fri, 16 Feb 2018 12:31:55 -0600 - rev 757264
Push 99729 by bmo:tom@mozilla.com at Tue, 20 Feb 2018 14:53:30 +0000
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
20f4b0d31dfc068414cdfeec8d310ee0f1ab8d44: Bug 1438482 - logErrorInPage should produce an error log; r=bgrins draft
Jan Odvarko <odvarko@gmail.com> - Tue, 20 Feb 2018 15:48:56 +0100 - rev 757263
Push 99728 by jodvarko@mozilla.com at Tue, 20 Feb 2018 14:51:19 +0000
Bug 1438482 - logErrorInPage should produce an error log; r=bgrins MozReview-Commit-ID: Ly9kDNwGthG
e05eb48c6beae6c4178a8edfd4476a0d17e563c4: Bug 1399242 - Do not render if the Net panel isn't currently selected; r=ochameau draft
Jan Odvarko <odvarko@gmail.com> - Tue, 20 Feb 2018 15:42:49 +0100 - rev 757262
Push 99728 by jodvarko@mozilla.com at Tue, 20 Feb 2018 14:51:19 +0000
Bug 1399242 - Do not render if the Net panel isn't currently selected; r=ochameau MozReview-Commit-ID: KdXkyt49upL
80d50fe4c946ef141b320cb1d5db71f1acbb8ebf: Bug 1439358 - Part 7 - Change how visibility is controlled so knownViews can be removed. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Tue, 20 Feb 2018 14:23:46 +0000 - rev 757261
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
Bug 1439358 - Part 7 - Change how visibility is controlled so knownViews can be removed. r=Gijs MozReview-Commit-ID: 9dVZ1cOto8O
6414af81fda088f486906986d1990ed020185a59: Bug 1439358 - Part 6 - Close the main view synchronously before opening it in a different panel. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Mon, 19 Feb 2018 15:53:59 +0000 - rev 757260
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
Bug 1439358 - Part 6 - Close the main view synchronously before opening it in a different panel. r=Gijs MozReview-Commit-ID: FciQH815F95
0675b1670a6415faaf4b3eb7e653246ce5879e8b: Bug 1439358 - Part 5 - Decouple view events from view visibility. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Tue, 20 Feb 2018 12:15:32 +0000 - rev 757259
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
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
41d8a7bee2452a35a5445c5239ecfbaaafbf5081: Bug 1439358 - Part 4 - Handle panel hiding during ViewShowing events. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Mon, 19 Feb 2018 12:01:34 +0000 - rev 757258
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
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
f0064b073a58ff50d58d714f00bf465e7b9876f1: Bug 1439358 - Part 3 - Open views before the transition and close them after it. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Thu, 15 Feb 2018 15:52:37 +0000 - rev 757257
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
Bug 1439358 - Part 3 - Open views before the transition and close them after it. r=Gijs MozReview-Commit-ID: 1VoIImxVTDN
d24fca8b06b9fd2b81508b3b764c32470ce1a5f1: Bug 1439358 - Part 2 - Always raise ViewShowing events and don't update the "current" property. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Mon, 19 Feb 2018 11:17:52 +0000 - rev 757256
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
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
5ab729430bbe5ab00a345f10e97c07739254e1dc: Bug 1439358 - Part 1 - Support "panelview" elements located anywhere in the document. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Mon, 12 Feb 2018 16:44:00 +0000 - rev 757255
Push 99727 by paolo.mozmail@amadzone.org at Tue, 20 Feb 2018 14:27:00 +0000
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
16c65f7f88b3b05da4094e456509481d667496f0: Bug 1438892 - Update bindings for API change in WR PR 2435. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 20 Feb 2018 09:06:50 -0500 - rev 757254
Push 99726 by kgupta@mozilla.com at Tue, 20 Feb 2018 14:08:06 +0000
Bug 1438892 - Update bindings for API change in WR PR 2435. r?jrmuizel MozReview-Commit-ID: EVw2PhfDAmf
444c6409efa5ba64fb86642dff8f7517a1540f0c: Bug 1438892 - Update reftest results for changes from WR PR 2423. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 20 Feb 2018 09:06:41 -0500 - rev 757253
Push 99726 by kgupta@mozilla.com at Tue, 20 Feb 2018 14:08:06 +0000
Bug 1438892 - Update reftest results for changes from WR PR 2423. r?jrmuizel MozReview-Commit-ID: LAqklCRsg8Y
bb2e21e61b9bce6c7e1dfa7435f90fa0248fe94b: Bug 1438892 - Update annotations from WR PR 2426. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 20 Feb 2018 09:06:32 -0500 - rev 757252
Push 99726 by kgupta@mozilla.com at Tue, 20 Feb 2018 14:08:06 +0000
Bug 1438892 - Update annotations from WR PR 2426. r?jrmuizel MozReview-Commit-ID: 5o3YCJKxlje
3545fa3c2eaca65653ab3b7bb98d98b4e44f7b26: Bug 1438892 - Update reftest fuzziness for WR PR 2405. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 20 Feb 2018 09:05:54 -0500 - rev 757251
Push 99726 by kgupta@mozilla.com at Tue, 20 Feb 2018 14:08:06 +0000
Bug 1438892 - Update reftest fuzziness for WR PR 2405. r?jrmuizel MozReview-Commit-ID: HcOke96a4Z2
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip