76942aa9741f2ce59f6208cfb0699ad3718a25d4: Bug 1321471. Part 1 - Use of MozPromise::ThenPromise() in place of CompletionPromise(). r=jya. draft
JW Wang <jwwang@mozilla.com> - Wed, 30 Nov 2016 18:19:26 +0800 - rev 446888
Push 37915 by jwwang@mozilla.com at Fri, 02 Dec 2016 02:48:36 +0000
Bug 1321471. Part 1 - Use of MozPromise::ThenPromise() in place of CompletionPromise(). r=jya. MozReview-Commit-ID: INbGpzwK4f9
2d0ae16d6ae4e9f2fd1ab35d94e6a24d4a473e88: Bug 1319007 - Add a watchdog to monitor long running tasks in TaskQueue. draft
JW Wang <jwwang@mozilla.com> - Thu, 24 Nov 2016 21:37:43 +0800 - rev 446887
Push 37915 by jwwang@mozilla.com at Fri, 02 Dec 2016 02:48:36 +0000
Bug 1319007 - Add a watchdog to monitor long running tasks in TaskQueue. MozReview-Commit-ID: 3CetAp30sCp
1d603d42ee817a805f3259232400f0a7eafcf829: Bug 1318226 - add gtest TestTaskQueue. draft
JW Wang <jwwang@mozilla.com> - Thu, 17 Nov 2016 14:25:53 +0800 - rev 446886
Push 37915 by jwwang@mozilla.com at Fri, 02 Dec 2016 02:48:36 +0000
Bug 1318226 - add gtest TestTaskQueue. MozReview-Commit-ID: 9Eg2ALRsV9j
b9f93169b724606dd77fc1810457ae3abc544c98: enable some EME tests. draft
JW Wang <jwwang@mozilla.com> - Tue, 15 Nov 2016 17:59:55 +0800 - rev 446885
Push 37915 by jwwang@mozilla.com at Fri, 02 Dec 2016 02:48:36 +0000
enable some EME tests. MozReview-Commit-ID: 60UjutEjQf9
6f39c69810f258b4108f8ee88048c5b690a503a2: Bug 1321614 - fix android_stuff kind to use build secrets, because it uses the same mozharness stuff as build jobs. r=dustin a=bustage
Justin Wood <Callek@gmail.com> - Thu, 01 Dec 2016 14:13:16 -0500 - rev 446884
Push 37915 by jwwang@mozilla.com at Fri, 02 Dec 2016 02:48:36 +0000
Bug 1321614 - fix android_stuff kind to use build secrets, because it uses the same mozharness stuff as build jobs. r=dustin a=bustage MozReview-Commit-ID: D6wV1KSa6mp
fa81bb472c6b47046fb1ed33442bee37aabc6a94: Bug 1301305 - Add tests for transform animations synchronized with geometric animations: r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:25:57 +0900 - rev 446883
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Add tests for transform animations synchronized with geometric animations: r?hiro MozReview-Commit-ID: Ay7xqfyW0N2
b27f45269cee6a86c8de7caa1c6133aa7532ef9d: Bug 1301305 - Notify animations when they should synchronize with geometric animations; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:21:11 +0900 - rev 446882
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Notify animations when they should synchronize with geometric animations; r?hiro MozReview-Commit-ID: 9Ploi5UwseA
1eb23bde782898f8d4d4fb401ba0b38a8754c0e4: Bug 1301305 - Add a member to track if an animation needs to be synchronized with geometric animations or not; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:19:10 +0900 - rev 446881
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Add a member to track if an animation needs to be synchronized with geometric animations or not; r?hiro Note that in this patch, the mSyncWithGeometricAnimations member is never set to true since no one calls NotifyGeometricAnimationsStartingThisFrame yet. MozReview-Commit-ID: GSTQmfkSdoy
171b032183fe4d9f40f07e4bea305b1474c4ea9e: Bug 1301305 - Factor out check for main-thread synchronization to a method on Animation; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:13:06 +0900 - rev 446880
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Factor out check for main-thread synchronization to a method on Animation; r?hiro This should be easier to read and provide us a convenient place to check for other cases where we need to synchronize with the main thread (such as the change introduced in this bug where we synchronize with other animations started at the same time). MozReview-Commit-ID: 8iuA7P4ycwM
e078a2b40b216e9c435d956ea7d36c8b35c625e7: Bug 1301305 - Extend PendingAnimationTracker to report if it contains play-pending geometric animations; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:10:44 +0900 - rev 446879
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Extend PendingAnimationTracker to report if it contains play-pending geometric animations; r?hiro We will use this later in this patch series to determine when we need to force transform animations to run on the main thread. The approach here is to lazily check if we have such animations. This allows animations to be modified after being added to the pending animation tracker (but not after HasPlayPendingGeometricAnimations is called since we cache the result at that point) and avoids poor performance when calling RemovePlayPending. MozReview-Commit-ID: LRLpCRnzvw
9a76870ce3566d0bf33158545c16c3ed3e2f3ce4: Bug 1301305 - Add Animation::AnimatesGeometry() helper to identify animations that animate geometric properties; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:04:08 +0900 - rev 446878
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Add Animation::AnimatesGeometry() helper to identify animations that animate geometric properties; r?hiro MozReview-Commit-ID: 7Q6wvm7ddxy
577e84807900fa74e0d33093dd193b8a27b2577e: Bug 1301305 - Add a performance warning type for transform animations that should be synchronized with geometric animations; r?hiro, r?flod draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:00:51 +0900 - rev 446877
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Add a performance warning type for transform animations that should be synchronized with geometric animations; r?hiro, r?flod This patch adds a new performance warning type for the case when we start a transform animation at the same time as an animation that includes a geometric property. In that case we run the transform animation on the main thread so that it is synchronized with the geometric animation (which we can only run on the main thread). This differs from CompositorAnimationWarningTransformWithGeometricProperties in that this applies across different elements whilst the existing warning only covers the case when the same animation animates both transform and geometric properties. MozReview-Commit-ID: EcOMo4VDAYY
a8e1c52d51b4c413f6256c65318e447b0d0e8480: Bug 1301305 - Make DevTools tests that expect all animation properties to run on the compositor use 'opacity'; r=pbro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 09:02:40 +0900 - rev 446876
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Make DevTools tests that expect all animation properties to run on the compositor use 'opacity'; r=pbro In subsequent patches in this bug we will change the heuristics for determining which transform animations run on the compositor. As a result some assumptions in DevTools tests about which animations run on the compositor will change. Since the heuristics for transform animations are more complex than opacity animations, in this patch we just switch those animations to use opacity instead (and add an animation rule that clearly marks that it expects all its properties to run on the compositor). MozReview-Commit-ID: FfDUAzKJRCz
4204af3343d99af7047d817a662abfc534ba7a7e: Bug 1301305 - Expand the set of geometric properties to include margin and padding properties; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 09:00:05 +0900 - rev 446875
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Expand the set of geometric properties to include margin and padding properties; r?hiro If margin or padding is being animated then we should synchronize with transform animations. Originally I included the border-*-width properties in this set. However I removed them because: 1. Generally animations of border-width are more subtle and it won't be noticeable if they are not synchronized with transform animations. 2. If authors animate the border shorthand (e.g. border: 1px blue -> 1px black) we will end up interpolating each of the longhands (including the widths despite there being no change) and yet such an animation does not really need to be synchronized with transform animations. Until we add code to workaround that it seems best to ignore border properties. I have verified that the tests added in this patch fail without the code changes in this patch. MozReview-Commit-ID: AJiDAvTpFuN
5298fa59db521984df71df4124fe3841af1e86bd: Bug 1301305 - Move propertyToIDL to testcommon.js; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 08:58:19 +0900 - rev 446874
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Move propertyToIDL to testcommon.js; r?hiro We would like to use this method in the next patch. MozReview-Commit-ID: CSdwlVInyds
553889f1a49cb74e0bb6de4b545b1488b8383999: Bug 1301305 - Rename assert_property_state_on_compositor to assert_all_properties_running_on_compositor; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 08:56:42 +0900 - rev 446873
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Rename assert_property_state_on_compositor to assert_all_properties_running_on_compositor; r?hiro Currently we have: assert_animation_property_state_equals assert_animation_property_state_on_compositor and it's not clear what the difference is. This patch renames the latter to make it clear it is testing that all properties are running on the compositor. MozReview-Commit-ID: 3PRm8fse9UI
a498827d72fd91ec21471a1e11920b7de15f55c1: Bug 1301305 - Move test data alongside the test function; r?hiro draft
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 08:56:29 +0900 - rev 446872
Push 37914 by bbirtles@mozilla.com at Fri, 02 Dec 2016 02:20:18 +0000
Bug 1301305 - Move test data alongside the test function; r?hiro Currently these tests are hard to read because the test data is separated from the test function so it's not clear what each of the fields mean or how to use it. This patch just brings the test data and test functions alongside one-another so they are easier to read. MozReview-Commit-ID: EzFLDG4YiXh
d26cd5daa9da149e362b8668154db07c74c84fc9: Bug 1321640: Part 2 - Clean up the header block and param parsing code. r?mixedpuppy draft
Kris Maglione <maglione.k@gmail.com> - Thu, 01 Dec 2016 13:11:08 -0800 - rev 446871
Push 37913 by maglione.k@gmail.com at Fri, 02 Dec 2016 02:15:14 +0000
Bug 1321640: Part 2 - Clean up the header block and param parsing code. r?mixedpuppy MozReview-Commit-ID: 9fI5JQWCVop
6c0e22e89a3274cb28717651b5e5703880f8473e: Bug 1321640: Part 1 - Clean up the general code flow so that it can be followed. r?mixedpuppy draft
Kris Maglione <maglione.k@gmail.com> - Thu, 01 Dec 2016 18:14:18 -0800 - rev 446870
Push 37913 by maglione.k@gmail.com at Fri, 02 Dec 2016 02:15:14 +0000
Bug 1321640: Part 1 - Clean up the general code flow so that it can be followed. r?mixedpuppy MozReview-Commit-ID: GmIWeZIprN0
d958f1b0bc56d48024fcfed5782ac79c7287830f: Bug 1320705: P7. Ensure audio decoder is recreated when chaining encountered. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 02 Dec 2016 12:28:28 +1100 - rev 446869
Push 37912 by bmo:jyavenard@mozilla.com at Fri, 02 Dec 2016 01:46:41 +0000
Bug 1320705: P7. Ensure audio decoder is recreated when chaining encountered. r?gerald The Opus decoder will error if we feed it new data if it has seen the last packet of a stream. MozReview-Commit-ID: Kw3cZuEKxie
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip