This patch introduces a new functions named HasEffectiveAnimationOfProperty.
This function checks that a given CSS property is overridden by !important
rules.
On the other hand, now KeyframeEffetReadOnly::HasAnimationOfProperty() does
just check that the effect has a given CSS property. This is used to create
a stacking context because we should create a stacking context for opacity or
transform animations even if the property is overridden by !important rules.
Note about no-stacking-context-(opacity|transform)-removing-animation-in-delay.html
Before this patch we don't create any stacking context for animations overridden
by !important rules, but after this patch we do create a stacking context for
such animations. As a result, in the test case we did paint a stacking context
in the first rAF callback and then in the second rAF callback we did clear the
painted stacking context. Unfortunately sometimes the second rAF callback was
called prior to clear the stacking context on the compositor because of
compositor delay. To avoid this situation, we have to wait for MozAfterPaint
instead of rAF callback.
MozReview-Commit-ID: AG1Y0IgoB3U
These tests aim to confirm that part 5 does not cause any regressons.
MozReview-Commit-ID: BtZ1OGiilmQ
--HG--
rename : layout/reftests/css-animations/no-stacking-context-animation-ref.html => layout/reftests/css-transitions/no-stacking-context-transition-ref.html
rename : layout/reftests/css-animations/stacking-context-animation-ref.html => layout/reftests/css-transitions/stacking-context-transition-ref.html
This is refcounted as we'll need to hold strong references to the ImageTracker
from style structs that load images.
MozReview-Commit-ID: 994gE9tOjAn
--HG--
extra : rebase_source : 2d50059e51b42251c89a92a954cef7b49720ceba
Adds console.dirxml support, which behave the same as console.log.
Adds mocha test to ensure dirxml calls are rendered as expected.
MozReview-Commit-ID: 22kUozOiDAA
--HG--
extra : rebase_source : 9d910136966b2a082150c58cc9ec28f04d47c30f
Deprecated ImageBitmapRenderingContext.transferImageBitmap and replaced
it with ImageBitmapRenderingContext.transferFromImageBitmap.
MozReview-Commit-ID: BbNgKrluhT7
--HG--
extra : rebase_source : 2aa3dbfc3acc5d8b1e451111ddbb2cac63f40433
This patch adds a new pref, which controls the minimum velocity required on a fling
for it to accelerate a previous fling. This makes it so that a fast fling followed
by a very slow fling doesn't get accelerated. Also, update the AndroidAPZ code
to respect the pre-existing fling acceleration interval pref, which disallows
fling acceleration/flywheel if the two flings are too far apart in time.
MozReview-Commit-ID: EfBUx5UV6VG
Jean-Yves Avenard
Hiroyuki Ikezoe
Tim Huang
Steven Englehardt
Cameron McCormack
Ronald S. Bultje
Jan Odvarko
Nicolas Chevobbe
Sebastian Hengst
Ryan VanderMeulen
Morris Tseng
Alessio Placitelli
Kartikaya Gupta
David Anderson
André Bargull
Sotaro Ikeda
Makoto Kato
Chris Peterson
Ehsan Akhgari
Phil Ringnalda
Iris Hsiao