692be37dcea532533ee7fad2020222722c197d09: Bug 1442604 - Add tests for the select and autocompletion popups used in an extension devtools panels. draft
Luca Greco <lgreco@mozilla.com> - Fri, 20 Apr 2018 19:16:27 +0200 - rev 787079
Push 107628 by luca.greco@alcacoop.it at Tue, 24 Apr 2018 06:49:27 +0000
Bug 1442604 - Add tests for the select and autocompletion popups used in an extension devtools panels. MozReview-Commit-ID: 5ov2YaeQV8V
4e7437e1d5329277e6d01d97226cbd1486b3c17b: Bug 1442604 - Split WebExtension devtools theme API tests in a separate test file. draft
Luca Greco <lgreco@mozilla.com> - Tue, 17 Apr 2018 16:05:02 +0200 - rev 787078
Push 107628 by luca.greco@alcacoop.it at Tue, 24 Apr 2018 06:49:27 +0000
Bug 1442604 - Split WebExtension devtools theme API tests in a separate test file. MozReview-Commit-ID: 6iOpBeSQZQo
68a775e1dab2d16fb7e2e95aa90d8f1a355ba42f: Bug 1455999 - Enable animation tests on WebRender. r?kats draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 15:25:52 +0900 - rev 787077
Push 107627 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:26:11 +0000
Bug 1455999 - Enable animation tests on WebRender. r?kats MozReview-Commit-ID: xtQbHwAHXT
c74ed0a23d1a600314a8d1253dcd967a92332c07: Bug 1455999 - Skip the visibility hidden test case on WebRender. r?birtles draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 15:25:41 +0900 - rev 787076
Push 107627 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:26:11 +0000
Bug 1455999 - Skip the visibility hidden test case on WebRender. r?birtles On WebRender, the animation on the visibility hidden element runs on the compositor somehow. MozReview-Commit-ID: 77dVlIeFQ3u
5a1c0a0d831c3733a40696e10e2843e1737bbd7e: Bug 1456003 - Don't allocate new AnimatedValue when we update AnimatedValue. r?kats draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 15:13:10 +0900 - rev 787075
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
Bug 1456003 - Don't allocate new AnimatedValue when we update AnimatedValue. r?kats We need to allocate new AnimatedValue only if there is no AnimatedValue corresponding to the id in the hashtable. MozReview-Commit-ID: HeRt74Tnojt
ea9667541dbdb57015aa5118817554918a54d622: [mq]: discard draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 14:35:42 +0900 - rev 787074
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
[mq]: discard MozReview-Commit-ID: 4BYsCgA98S0
14740d9d8cae805e9cd5ab990b25864f19c21820: Bug 1437036 - Implement GetLastTransactionId in WebRenderLayerManager. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 06 Apr 2018 15:14:02 -0400 - rev 787073
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
Bug 1437036 - Implement GetLastTransactionId in WebRenderLayerManager. r?sotaro MozReview-Commit-ID: CLymsb5w3pk
2cfe304328a770ca09c6e4a2da8ef7ce91ec4896: Bug 1454324 - Skip calculating animation value if animation's progress value hasn't been changed since the last composition and if there are no other animations on the same element. r?birtles,kats draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 13:52:19 +0900 - rev 787072
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
Bug 1454324 - Skip calculating animation value if animation's progress value hasn't been changed since the last composition and if there are no other animations on the same element. r?birtles,kats Note that we have to calculate animation values if there is another animation since the other animation might be 'accumulate' or 'add', or might have a missing keyframe (i.e. the calculated animation values will be used in the missing keyframe). MozReview-Commit-ID: rQyS9nuVJi
8174acca40844508f2fabf20387631dc4a04e44f: Bug 1454324 - Set non-animated values to the layer only if there is no running animation. r?kats draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 13:52:19 +0900 - rev 787071
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
Bug 1454324 - Set non-animated values to the layer only if there is no running animation. r?kats In the next patch, we skip updating animation value for the layer if the animation value isn't changed. So without this patch, we will have to update animation value even if the value isn't changed at all. MozReview-Commit-ID: 9tU7BTkNOHL
9fdb39297726a66a110d04a564c411c81eb4759b: Bug 1454324 - Clear all animation data when we release layer. r?kats draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 13:52:19 +0900 - rev 787070
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
Bug 1454324 - Clear all animation data when we release layer. r?kats MozReview-Commit-ID: AOGNjLesY0t
c7d892159ef875cf385c0d8c88233c900a09e5dc: Bug 1454324 - Cache animation TimingParams on the compositor. r?birtles draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 24 Apr 2018 13:52:18 +0900 - rev 787069
Push 107626 by hikezoe@mozilla.com at Tue, 24 Apr 2018 06:13:40 +0000
Bug 1454324 - Cache animation TimingParams on the compositor. r?birtles We don't need to calculate TimingParams each time we compose an animation on the compositor because TimingParams is immobile since the animation was sent to the compositor. MozReview-Commit-ID: 3rfzkdGClES
b47b3a6f6ae83853f198aab3137fe8cfd28bd582: Bug 1348145 - Remove getWindowPosition/setWindowPosition and getWindowSize/setWindowSize. r?whimboo draft
Venkatesh Pitta <venkateshpitta@gmail.com> - Tue, 24 Apr 2018 15:53:07 +1000 - rev 787068
Push 107625 by bmo:venkateshpitta@gmail.com at Tue, 24 Apr 2018 05:56:31 +0000
Bug 1348145 - Remove getWindowPosition/setWindowPosition and getWindowSize/setWindowSize. r?whimboo MozReview-Commit-ID: CUCyyyjZHVG
baeaa9e3e5373f10b6ec0327e325d0a54de2abe2: Bug 1455589 - Drop margin at right end of DevTools toolbox toolbar on non-Mac platforms; r?jryans draft
Brian Birtles <birtles@gmail.com> - Tue, 24 Apr 2018 14:41:44 +0900 - rev 787067
Push 107624 by bmo:bbirtles@mozilla.com at Tue, 24 Apr 2018 05:42:25 +0000
Bug 1455589 - Drop margin at right end of DevTools toolbox toolbar on non-Mac platforms; r?jryans This margin only appears to be needed on Mac hence this patch makes the setting apply only on OSX. It also: * Updates the margin from 3px to 4px since it seems that was the original intention.[1] * Switches to using logical properties so that the margin appears in the correct place in RTL builds. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1455589#c1 MozReview-Commit-ID: Chp1HJcretg
7f013406253d30eada49e130860996be1122d31b: Bug 1456037 - Test that documents gesture activate on key/mouse down instead of up. r=masayuki draft
Chris Pearce <cpearce@mozilla.com> - Mon, 23 Apr 2018 15:53:25 +1200 - rev 787066
Push 107623 by bmo:cpearce@mozilla.com at Tue, 24 Apr 2018 05:36:56 +0000
Bug 1456037 - Test that documents gesture activate on key/mouse down instead of up. r=masayuki MozReview-Commit-ID: AGZM0JdSUDv
edf5673be59a3714c3dd4eb239efd17d6a91ec32: Bug 1456037 - Gesture activate documents on key/mouse down not up. r=masayuki draft
Chris Pearce <cpearce@mozilla.com> - Mon, 23 Apr 2018 15:56:29 +1200 - rev 787065
Push 107623 by bmo:cpearce@mozilla.com at Tue, 24 Apr 2018 05:36:56 +0000
Bug 1456037 - Gesture activate documents on key/mouse down not up. r=masayuki We should gesture activate documents in key/mouse down instead of up because if a web app wants to play a video inside a key/mouse handler, the document needs to be activated before the handler runs. Also, Chrome activates on key/mouse down, so we may have compat issues if we have different behaviour. MozReview-Commit-ID: JgGaQcNQfzz
e54fd11d873dd85d95d2f5baa2f998c8621e1be9: Bug 1456209 - 3. Scale timeouts based on device; r?gbrown draft
Jim Chen <nchen@mozilla.com> - Tue, 24 Apr 2018 01:31:09 -0400 - rev 787064
Push 107622 by bmo:nchen@mozilla.com at Tue, 24 Apr 2018 05:31:52 +0000
Bug 1456209 - 3. Scale timeouts based on device; r?gbrown Scale the default test timeout based on the architecture, and whether we're running inside an emulator or on a real device. This is done to account for performance differences in the device under test. We have some tests that are expected to timeout. In order to maintain accuracy of these tests across devices, their custom timeout values are scaled as well. MozReview-Commit-ID: 67RrOchPoPz
66d6ca6e3850d5b6b21cbe7b6fe2297bad4e7605: Bug 1456209 - 2. Miscellaneous GeckoSessionTestRule changes; r=me draft
Jim Chen <nchen@mozilla.com> - Tue, 24 Apr 2018 01:31:09 -0400 - rev 787063
Push 107622 by bmo:nchen@mozilla.com at Tue, 24 Apr 2018 05:31:52 +0000
Bug 1456209 - 2. Miscellaneous GeckoSessionTestRule changes; r=me Miscellaneous small fixes to GeckoSessionTestRule, including: * Make some internal assertions _not_ go through the error collector, because by not throwing an exception at the time of the assertion, we may end up with another, less clear exception down the road. * Make timeout throw a distinct TimeoutException, so that tests that expect an AssertionError would not mistakenly pass due to a timeout. * Use the default timeout value for operations internal to the test harness, so that internal operations are not affected when using a custom timeout value. * Print the longest actual wait duration to logcat, so that it's easier to adjust timeout values in the future. * Wait for initial about:blank load for non-e10s as well, due to recent changes in GV startup code. MozReview-Commit-ID: 2uy2EVpl2gl
6adb3de23ef8f0866cea4b1036ee5a8117dfa9d7: Bug 1456209 - 1. Fix test license headers; r=me draft
Jim Chen <nchen@mozilla.com> - Tue, 24 Apr 2018 01:31:08 -0400 - rev 787062
Push 107622 by bmo:nchen@mozilla.com at Tue, 24 Apr 2018 05:31:52 +0000
Bug 1456209 - 1. Fix test license headers; r=me Keep test harness code under MPL, but release actual test cases into the public domain in accordance with Mozilla's license policy. MozReview-Commit-ID: E7108uN5TnW
338894042a359dc68ab7fcf0faa46978c61cbf0d: Bug 1456381 - TSFTextStore should discard pending composition update actions before recording composition end action r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 19 Apr 2018 20:42:00 +0900 - rev 787061
Push 107621 by masayuki@d-toybox.com at Tue, 24 Apr 2018 05:24:57 +0000
Bug 1456381 - TSFTextStore should discard pending composition update actions before recording composition end action r?m_kato TSFTextStore should discard pending composition update actions when it records end composition update action because end composition update action causes dispatching eCompositionCommit event and it replaces old composition string anyway. So, following eCompositionChange which is dispatched by preceding composition update actions are just redundant. MozReview-Commit-ID: HBHx2jA15ro
a37bc05356f56f3cd6e357f0e69a0dabd8c14dab: Bug 1456209 - 3. Scale timeouts based on device; r?gbrown draft
Jim Chen <nchen@mozilla.com> - Tue, 24 Apr 2018 01:16:38 -0400 - rev 787060
Push 107620 by bmo:nchen@mozilla.com at Tue, 24 Apr 2018 05:17:28 +0000
Bug 1456209 - 3. Scale timeouts based on device; r?gbrown Scale the default test timeout based on the architecture, and whether we're running inside an emulator or on a real device. This is done to account for performance differences in the device under test. We have some tests that are expected to timeout. In order to maintain accuracy of these tests across devices, their custom timeout values are scaled as well. MozReview-Commit-ID: ENWeXAzV31u
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip