TransformValue and TransformComponent asMatrix methods should return DOMMatrix.

[shans]

[heycam]

Note that I think we still need Matrix, as we want an object that represents a single matrix(...) value in a transform list. But also I don't think we want matrix to duplicate (and be different from) DOMMatrix's interface. For example DOMMatrix uses m11, m12, etc. for 3D components rather than a, b, ...

Should Matrix be something like:

interface Matrix : TransformComponent {
  readonly attribute DOMMatrixReadOnly matrix;
};

and if so, should we keep a constructor on Matrix and make it have the same arguments as DOMMatrix's constructor arguments?

[shans]

I would be quite happy for Matrix to only have a constructor that takes a
DOMMatrix. It would be easy to add extra constructors later if we felt the
need.

On Sun, 31 Jan 2016 at 10:08 Cameron McCormack notifications@github.com
wrote:

Note that I think we still need Matrix, as we want an object that
represents a single matrix(...) value in a transform list. But also I
don't think we want matrix to duplicate (and be different from) DOMMatrix's
interface. For example DOMMatrix uses m11, m12, etc. for 3D components
rather than a, b, ...

Should Matrix be something like:

interface Matrix : TransformComponent {
DOMMatrixReadOnly matrix;
};

and if so, should we keep a constructor on Matrix and make it have the
same arguments as DOMMatrix's constructor arguments
https://drafts.fxtf.org/geometry/#DOMMatrix?

—
Reply to this email directly or view it on GitHub
#103 (comment)
.

[shans]

Oh, this is done.