- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 27 Apr 2016 17:48:57 -0700
- To: Brian Birtles <bbirtles@mozilla.com>
- Cc: Simon Fraser <smfr@me.com>, "www-style@w3.org list" <www-style@w3.org>
On Wed, Apr 27, 2016 at 5:02 PM, Brian Birtles <bbirtles@mozilla.com> wrote: > On 2016/04/28 8:23, Tab Atkins Jr. wrote: >> >> On Wed, Apr 27, 2016 at 4:16 PM, Brian Birtles <bbirtles@mozilla.com> >> wrote: >>> >>> On 2016/04/27 13:49, Brian Birtles wrote: >>>> >>>> I've noticed that IE and Edge appear to do this already.[2] Their >>>> behavior also differs in the test case Simon provided.[3] >>>> >>>> Since IE and Edge already do this, WebKit seems interested, and it would >>>> seem to provide performance advantages, any chance we could revisit >>>> this? >>> >>> >>> I should also mention that CSS Transitions create a stacking context >>> during >>> the delay phase in at least Blink, Gecko, Edge, and IE. >> >> >> Sigh, all right. In that case, let's specify that, when an >> animation/transition is active, the UA must act as if 'will-change' >> additionally includes all the properties involved. That answers all >> the questions about how this should act, since it's already been >> answered once. > > That suits me with the clarification that "active" excludes animations that > have finished and are not filling forwards. Yeah, by "active" I meant "running or filling". ~TJ
Received on Thursday, 28 April 2016 00:49:45 UTC