Re: [css-houdini-drafts] [css-typed-om] What to do with a 2d CSSMatrixComponent set to a 3d DOMMatrix?

The problem is that we need to distinguish between 2d and 3d transforms, and while some 3d transforms are obvious (those that are non-zero in the parts that only 3d cares about), some aren't (but they still need to trigger the extra UA work that 3d transforms cause).  Literal CSS is fine with this - the function name distinguishes them.  But we don't want to create separate interfaces for *all* the functions, as it's usually irrelevant. This is just the problematic one.

Throwing upon setting a definitely-3d matrix for a 2d matrix interface *sounds* nice, but it runs into the problem from the OP - the matrix is a sub-object that doesn't allow us to intercept its sets, so you can create an initially-2d matrix, create a CSSTransformMatrix from it, then mutate it to be 3d.  We've gotta do something about that, and just asking "is the matrix *currently* 2d-ish or 3d-ish" doesn't work well.

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

Received on Wednesday, 3 May 2017 23:09:45 UTC