Re: [fxtf-drafts] [css-geometry] `DOMMatrixReadonly` stringifier does not stringify all matrix elements. (#574)
[fxtf-drafts] [geometry-1] setting a matrix to identity with setters keeps is2D `true`. Creating a matrix with a 16-number identity sequence sets `is2D` to `false`. (#588)
[fxtf-drafts] [geometry-1] `DomMatrixReadOnly` is missing `preMultiply()` method (and the idea of better mutable vs immutable patterns) (#587)
[fxtf-drafts] [geometry-1] Methods of immutable classes should return immutable instances. (#586)
Re: [fxtf-drafts] [geometry] return DOMPoint or DOMPointReadOnly accordingly, from matrixTransform method? (#275)
[fxtf-drafts] [geometry-1] propose adding DOMPoint as an argument for DOMMatrix that accepts vectors. (#585)
[fxtf-drafts] [geometry-1] There is no way to reset `DOMMatrix` `is2D` back to `true` when returning to identity. (#584)
[fxtf-drafts] Pull Request: Improve links to 2D vs 3D transforms math descriptions.
[fxtf-drafts] [geometry-1] Why does `multiplySelf` just accept another `DOMMatrix`? (#582)
Re: [fxtf-drafts] [geometry] DOMMatrix/DOMMatrix could use more methods and helpers. (#194)
[fxtf-drafts] [geometry-1] What's the point of `DOMMatrixInit` if the `constructor` cannot accept such a value? (#581)
[fxtf-drafts] [geometry-1] Steps for `multiplySelf` are inefficient (#580)
[fxtf-drafts] Improve algorithm steps for identity transforms (#579)
- Re: [fxtf-drafts] Improve algorithm steps for identity transforms (#579)
- Re: [fxtf-drafts] [geometry-1] Improve algorithm steps for identity transforms (#579)