You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
Uh oh!
There was an error while loading. Please reload this page.
.. and non-none values should establish a stacking context & containing block for consistency with transforms 1.
Spec link: https://drafts.csswg.org/css-transforms-2/#individual-transforms
The text was updated successfully, but these errors were encountered: