Skip to content

[css-transforms-2] individual transform properties should have default value of 'none'. #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
shans opened this issue Jun 26, 2016 · 3 comments

Comments

@shans
Copy link
Contributor

shans commented Jun 26, 2016

.. 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

@shans
Copy link
Contributor Author

shans commented Jun 26, 2016

email from Matt Rakow:

"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"

@shans
Copy link
Contributor Author

shans commented Jun 26, 2016

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.

@ChumpChief
Copy link
Member

I support the addition of a "none" value as the default for each of these properties. More discussion at:
http://lists.w3.org/Archives/Public/www-style/2016Jun/0170.html
http://lists.w3.org/Archives/Public/www-style/2016Jun/0171.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants