- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jan 2018 23:58:35 +0000
- To: public-houdini-archive@w3.org
The ["is2D design considerations" section](https://drafts.css-houdini.org/css-typed-om/#dom-csstransformcomponent-is2d) outlines some of the options we thought thru and rejected. I don't think there's any unambiguously good solution. I know we considered auto-setting the 3d-related components to 0 or whatever when is2D was true, but I don't recall why we rejected that. Maybe we thought it would be *more* surprising to set a translate.z attribute and then get a 0 when you read it back? I don't have a strong opinion on whether we should do that or not, I suppose. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/610#issuecomment-361776174 using your GitHub account
Received on Tuesday, 30 January 2018 23:58:37 UTC