- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Nov 2018 21:27:13 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `SVGTransform's setMatrix method should take a DOMMatrix2DInit`, and agreed to the following: * `RESOLVED: Replace DOMPoint with DOMPoint2DInit with SetMatrix() and createSVGTransformFromMatrix()` <details><summary>The full IRC log of that discussion</summary> <myles> TOPIC: SVGTransform's setMatrix method should take a DOMMatrix2DInit<br> <myles> GitHub: https://github.com/w3c/svgwg/issues/326<br> <myles> krit: we already changed the interface from DOMPointInit, that would pretty much be the same thing, except DomMatrixReadOnly to DOMMatrix2DInit<br> <myles> AmeliaBR: the only question: Whether those methods copy the matrix or create a new matrix with the same data<br> <myles> AmeliaBR: whether they reference the exact same data or create a copy of it<br> <myles> krit: they currently do not reference the object<br> <myles> krit: in your terms, it would be a copy<br> <myles> AmeliaBR: it says it's do a new matrix, so it's not about preserving the exact object. so in that case no there's no reason not to be able to use a dictionary with the same properties as a matrix, it doesn't need to be a particular class type. Sounds good to me. There was another message .... ?<br> <myles> AmeliaBR: CreateTransformFrom <inaudible> okay, that sounds sane<br> <myles> RESOLVED: Replace DOMPoint with DOMPoint2DInit with SetMatrix() and createSVGTransformFromMatrix()<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/326#issuecomment-438034279 using your GitHub account
Received on Monday, 12 November 2018 21:27:15 UTC