W3C home > Mailing lists > Public > www-style@w3.org > June 2016

Re: [css-transforms] Individual transform properties, stacking contexts, containing blocks

From: Simon Fraser <smfr@me.com>
Date: Mon, 27 Jun 2016 10:18:56 -0700
Cc: Matt Rakow <marakow@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
Message-id: <B501E4F6-488E-40BA-9007-799C391C308D@me.com>
To: Shane Stephens <shans@google.com>
> On Jun 26, 2016, at 4:22 AM, Shane Stephens <shans@google.com> wrote:
> 
> Having a default 'none' (and every other value establishing a stacking context) is probably best so that animations that sweep through the zeroes (translate: 0px, rotate: 0deg, and scale: 1) don't pop in and out of stacking context/containing block.
> 
> Tracked here: https://github.com/w3c/csswg-drafts/issues/244 <https://github.com/w3c/csswg-drafts/issues/244>
> 
> 
> 
> On Sat, Jun 25, 2016 at 10:32 AM Matt Rakow <marakow@microsoft.com <mailto:marakow@microsoft.com>> wrote:
> Hi all,
> 
> Any non-"none" value for the transform property causes the element to establish a stacking context and containing block.  The individual transform properties are not currently specified as establishing either of these; should they (I think yes)?
> 
> If yes, when?  Do these properties also need a "none" value as the default?
> 
> Thanks,
> -Matt
> 

Didn't we decide that stacking context doesn't change during animations, as if will-change were applied if any keyframe has a transform?

Simon


Received on Monday, 27 June 2016 17:20:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:47 UTC