c2526f6786f074888d71c8e166a02aea3e19e75b: No bug, Automated HPKP preload list update from host bld-linux64-spot-570 - a=hpkp-update
ffxbld - Wed, 07 Dec 2016 06:27:07 -0800 - rev 325340
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
No bug, Automated HPKP preload list update from host bld-linux64-spot-570 - a=hpkp-update
438822713e70edbdad6fb00f75e96b2b9dc2fcaa: No bug, Automated HSTS preload list update from host bld-linux64-spot-570 - a=hsts-update
ffxbld - Wed, 07 Dec 2016 06:27:04 -0800 - rev 325339
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
No bug, Automated HSTS preload list update from host bld-linux64-spot-570 - a=hsts-update
c401d72933641748f3738e90e7bbe539705e2f1c: merge mozilla-inbound to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Wed, 07 Dec 2016 11:30:43 +0100 - rev 325338
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
merge mozilla-inbound to mozilla-central a=merge
f863d5050b3f71218c001804f97ca98474b2bae6: Bug 1257249 - Replace a use of cStringIO with StringIO to avoid a problem with old Python versions, r=Ms2ger
James Graham <james@hoppipolla.co.uk> - Tue, 06 Dec 2016 10:30:34 -1000 - rev 325337
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1257249 - Replace a use of cStringIO with StringIO to avoid a problem with old Python versions, r=Ms2ger MozReview-Commit-ID: D1wkrdaejQB
f0c1e6b61ded83d3b646f55bb0f7cabdf822912b: Bug 1301305 - Add tests for transform animations synchronized with geometric animations: r=hiro
Brian Birtles <birtles@gmail.com> - Mon, 05 Dec 2016 21:56:05 -1000 - rev 325336
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1301305 - Add tests for transform animations synchronized with geometric animations: r=hiro MozReview-Commit-ID: Ay7xqfyW0N2
aea2d20ddd3495a0519bf6f6891be66b2fc99e3b: Bug 1301305 - Notify animations when they should synchronize with geometric animations; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:21:11 +0900 - rev 325335
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1301305 - Notify animations when they should synchronize with geometric animations; r=hiro MozReview-Commit-ID: 9Ploi5UwseA
8f7a10d823e2dcc2fd9fa0a976443f4068ce7c1f: Bug 1301305 - Extend PendingAnimationTracker to mark play-pending animations if there are geometric animations starting at the same time; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:10:44 +0900 - rev 325334
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1301305 - Extend PendingAnimationTracker to mark play-pending animations if there are geometric animations starting at the same time; r=hiro 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
dc0424e6e32de0cfca4cd5a218f8b11c129ae388: Bug 1301305 - Add a member to track if an animation needs to be synchronized with geometric animations or not; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:19:10 +0900 - rev 325333
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
0a8a06811d79b1f8b8b7b961be055a1518bdb376: Bug 1301305 - Factor out check for main-thread synchronization to a method on Animation; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:13:06 +0900 - rev 325332
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
49a60bdadd4eeb1ac0594b095456f5566e499314: Bug 1301305 - Add AnimationEffectReadOnly::AffectsGeometry() helper to identify effects that animate geometric properties; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:04:08 +0900 - rev 325331
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1301305 - Add AnimationEffectReadOnly::AffectsGeometry() helper to identify effects that animate geometric properties; r=hiro MozReview-Commit-ID: 7Q6wvm7ddxy
d14b2103446d083f72f5262d79168e8eb539f401: Bug 1301305 - Add a performance warning type for transform animations that should be synchronized with geometric animations; r=hiro, r=flod
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 10:00:51 +0900 - rev 325330
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
ece7cb85c38122ec03a8870e2f0054ece2024fa0: Bug 1301305 - Make DevTools tests that expect all animation properties to run on the compositor use 'opacity'; r=pbro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 09:02:40 +0900 - rev 325329
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
9a3bdee53cec09705fdf604c0c0c93364eb16c2a: Bug 1301305 - Expand the set of geometric properties to include margin and padding properties; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 09:00:05 +0900 - rev 325328
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
aba14a8202e05d4c62b478ff9c61f0ac02dc8438: Bug 1301305 - Move propertyToIDL to testcommon.js; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 08:58:19 +0900 - rev 325327
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
aa5c5ad83b28d871837a3265d1b35fd2d75e8212: Bug 1301305 - Rename assert_property_state_on_compositor to assert_all_properties_running_on_compositor; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 08:56:42 +0900 - rev 325326
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
ca7fd1a24055581dbfcd48f2cd71b2abbbad33f3: Bug 1301305 - Move test data alongside the test function; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 02 Dec 2016 08:56:29 +0900 - rev 325325
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +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
40c8129cffbf82cd89b4e22caf52aa042b5573e4: Bug 1213977 - Don't reset an ongoing incremental GC if AutoKeepAtoms is set r=sfink
Jon Coppeard <jcoppeard@mozilla.com> - Tue, 06 Dec 2016 17:25:02 -1000 - rev 325324
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1213977 - Don't reset an ongoing incremental GC if AutoKeepAtoms is set r=sfink
c30011abb0f2357132b5098c2d3e2ce35b880a12: Bug 1322312 - Assert that GCRuntime::enter/leaveUnsafe region is only used on the main thread r=sfink
Jon Coppeard <jcoppeard@mozilla.com> - Tue, 06 Dec 2016 17:23:48 -1000 - rev 325323
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1322312 - Assert that GCRuntime::enter/leaveUnsafe region is only used on the main thread r=sfink
1d9ec0ad1388284030757003dbffa93bcaf9c0e0: Bug 1320817 - Move child process PAPZ initialization into TabChild::InitRenderingState. r=kats
Ryan Hunt <rhunt@eqrion.net> - Mon, 28 Nov 2016 22:21:27 -0600 - rev 325322
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1320817 - Move child process PAPZ initialization into TabChild::InitRenderingState. r=kats
5ee72d9b8e3ef32e4dceca79a0682641b7401b83: Bug 1321450 - Update tests.
Jeff Gilbert <jdashg@gmail.com> - Tue, 06 Dec 2016 14:44:36 -0800 - rev 325321
Push 24 by maklebus@msu.edu at Tue, 20 Dec 2016 03:11:33 +0000
Bug 1321450 - Update tests. MozReview-Commit-ID: FNIVogqXLld
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 tip