This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
https://drafts.fxtf.org/geometry/#ref-for-dom-dompointreadonly-w-1 [[ DOMPoint matrixTransform(optional DOMMatrixInit matrix); ]] Why not return DOMPoint or DOMPointReadOnly accordingly? For example, when implemented in JavaScript, then instead of ``` matrixTransform(matrix) { let result = new DOMPoint(this) } ``` we would write ``` matrixTransform(matrix) { let result = new this.constructor(this) } ``` so that it picks the right constructor.
Oh, and I am missing the rest of the implementation in those examples, just showing that we can create a new matrix based on which class is being used.
We could, but why? Note that DOMMatrixReadOnly's immutable transformation methods also return DOMMatrix rather than DOMMatrixReadOnly.
https://github.com/w3c/fxtf-drafts/issues/275