- From: Kevin Babbitt via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 19:00:17 +0000
- To: public-css-archive@w3.org
As I understand it, the one bit of web compatibility data we have is that WebKit regressed a site when they changed away from returning `none`. I also did some digging and found that an older version of the spec [1] defined "transformable element" in a way that excludes `display:none` elements, in which case `transform` would not apply to `display:none` elements, which I think makes it reasonable for the computed value to be `none`. So right now I'd favor the `none` option but would reconsider if more compatibility data surfaced. [1] https://www.w3.org/TR/2017/WD-css-transforms-1-20171130/#terminology -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9121#issuecomment-1906734795 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 19:00:21 UTC