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

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

From: Matt Rakow <marakow@microsoft.com>
Date: Mon, 27 Jun 2016 17:35:51 +0000
To: Simon Fraser <smfr@me.com>, Shane Stephens <shans@google.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <CY1PR0301MB204268BE354C909B4A67CE8FAD210@CY1PR0301MB2042.namprd03.prod.outlook.com>
> 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.

That sounds good to me.

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

The problem I see with an assumption like that is that we would still have to define the default values for each property as not establishing a stacking context outside of animations.  That would still lead to jumps for script-driven "animations".  Or for transitions that happen to start/end at a default value, which may be especially unpredictable/uncontrollable for transitioned values applied programmatically rather than through a static stylesheet.

Received on Monday, 27 June 2016 17:36:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:03 UTC