Re: [css-houdini-drafts] [css-typed-om] Does the is2D design allow for inconsistent interpretation of CSSTransformComponents?

The Working Group just discussed `[css-typed-om] Does the is2D design allow for inconsistent interpretation of CSSTransformComponents?`, and agreed to the following resolutions:

* `RESOLVED: keep last week resolution , say ignore instead of throw, and for matrix use the previous with an issue noting we'd like to enforce in the same way but we don't know how.`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-typed-om] Does the is2D design allow for inconsistent interpretation of CSSTransformComponents?<br>
&lt;dael> github: https://github.com/w3c/css-houdini-drafts/issues/610<br>
&lt;dael> TabAtkins: This needs revisit because I remembered the reason I made a choice.<br>
&lt;dael> TabAtkins: Short recap, dbaron suggested that is2D causes behavior changes so if it's set to true we throw on changes that would touch 3d parts of an object. Problem is matrx component. IT doesn't reinvent 2 or 3d objects on its own. I didn't want a low power of the dom matrix.<br>
&lt;dael> TabAtkins: So the matrix object just contains a dom matrix. Problem is dom matrix doesn't have this logic. is2D flag is read only and just reflects if it's 2d or 3d. There's no way for the is 2d flag on the transform to effect how the dom matrix responds to operations. There's nothing in the spec for it now and it would be a tear away problem. Things are linked in lifecycles which is awk for impl<br>
&lt;dael> TabAtkins: There's no way to do this thing on the matrix component as designed. We can't even split into 2 or 3d because the 2d will still want a mtrix.<br>
&lt;dael> TabAtkins: That's why I went htat is2D is a declaration from the author and we ignore the 3d ish parts rather then the more controlling way. So I think we need to revert unless someone has a more clever way<br>
&lt;dael> fremy: For dom we made the flag read only on purpose beccause different transversions where something looks 2d but is 3d.<br>
&lt;astearns> s/fremy/krit/<br>
&lt;dael> TabAtkins: Right. Same policy is elsewhere. A translate with 0 on the z axis is still 3d. It's a product of your intent not the contents. I agree the dom matrix isn't a bad design, it's trying to do a different thing then transform are trying to do.<br>
&lt;fremy> ^ +!<br>
&lt;fremy> ^ +1<br>
&lt;dael> dbaron: I'm not especially happy. It think it's worth leaving an issue to see if somebody can come up with something better.<br>
&lt;dael> TabAtkins: Yeah. If we're going to go with that I would prefer to change my rec from last week to ignore instead of throw since that'll be consistant with us coming up with a good way to do it that works.<br>
&lt;dael> TabAtkins: If we stick with the solution from before where is2d just changes serialization, if we can solve the matrix component then sets to 3d will do something and I'd prefer we do something in case it's stuck for an extended period of time.<br>
&lt;dael> TabAtkins: So ignore sets rather then throw.<br>
&lt;dael> astearns: Work for you dbaron ?<br>
&lt;dael> dbaron: I'm okay with that.<br>
&lt;dael> astearns: AS far as I understand suggestion is we keep previous resolution but change so we don't throw on sets<br>
&lt;dael> TabAtkins: Ultimate issue is I have no way to enforce the previous resolution on matrix. So keep last week, say ignore instead of throw, and for matrix use the previous with an issue notiing we'd like to enforce in the same way but we don't know how.<br>
&lt;dael> astearns: Obj to this path?<br>
&lt;dael> RESOLVED: keep last week resolution , say ignore instead of throw, and for matrix use the previous with an issue noting we'd like to enforce in the same way but we don't know how.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/610#issuecomment-365682780 using your GitHub account

Received on Wednesday, 14 February 2018 17:28:39 UTC