Граф коммитов

5 Коммитов

Автор SHA1 Сообщение Дата
Hiroyuki Ikezoe 5a20151f8c Bug 1310096 - Replace the wait for the second MozAfterPaint with rAF callback to avoid intermittent failure on Android. r=boris
MozReview-Commit-ID: AamMljHkbM4

--HG--
extra : rebase_source : ea018d81de4172a21e9089f688ab6d2624c6f4eb
2016-10-19 14:41:50 +09:00
Hiroyuki Ikezoe ff84f76fce Bug 1278136 - Part 5: Create a stacking context for opacity/transform animations even if it's in delay phase and even if the property is overridden by !important rules. r=birtles
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
2016-10-13 16:54:25 +09:00
Hiroyuki Ikezoe f110687f15 Bug 1278136 - Part 4: Tests to check stacking context for correct effect in cascading rule. r=birtles, bz
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
2016-10-12 09:59:02 +09:00
Phil Ringnalda 6182caa3b9 Backed out 2 changesets (bug 1278136) for failures in no-stacking-context-opacity-removing-animation-in-delay.html
Backed out changeset 62cf4a7d6007 (bug 1278136)
Backed out changeset 5f2db29e67ca (bug 1278136)

MozReview-Commit-ID: K9WcZFjL2XB
2016-10-11 20:40:36 -07:00
Hiroyuki Ikezoe 5443b7cdf5 Bug 1278136 - Part 4: Tests to check stacking context for correct effect in cascading rule. r=birtles, bz
These tests aim to confirm that part 5 does not cause any regressons.
Adding this bunch of reftests makes a slight change in the result of
layout/reftests/bugs/395107-2.html on Android, so fuzzy-if was also
added for the test.

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
2016-10-12 09:59:02 +09:00