I tracked down and reported a problem in Chrome's implementation of the DOMMatrix interface on Friday but I didn't set the "Component" sensibly and I think this may negatively affect it's visibility to the developers. I wasn't really sure what to set it to and presumed I, or someone else, could change it later, but this doesn't seem to be the case (at least, I don't appear to be able to change it). I don't really want to create a new bug that is basically a duplicate but with a sensible component so I'm posting here to get advice and/or bring the issue to someone's attention.
Basically, we are using a cross-browser wrapper class to set the transform used on an SVG use element and setting the m33 or m44 elements is being handled incorrectly. If they are set to 0 or -0 then is2D is not set to false but if they are set to anything else then is2D is set to false. These two elements should be testing against 1, not 0 or -0. This incorrect value of is2D causes the toString function to generate a matrix3d() rather than a matrix() and this doesn't work for SVG use elements. This is a pretty fundamental bug in the new implementation and I'm assuming the fix should be almost trivial so would really like to see it fixed before the release of 61.
So, can the component be changed to something sensible? I'm still not really sure what it should be, there is a geometry related one but it doesn't mention the new DOMMatrix interface (or other, related, interfaces). Is there any other way of bringing it to a relevant person's attention?
Thanks,
Gerry