- From: Karl Dubost via GitHub <noreply@w3.org>
- Date: Fri, 17 Apr 2026 09:09:38 +0000
- To: public-svg-issues@w3.org
karlcow has just labeled an issue for https://github.com/w3c/svgwg as "Needs tests": == currentTranslate on SVGSVGElement. Not covered by current WPT == - DOMPointReadOnly type: FAIL everywhere (expected — all return SVGPoint) - Read-only on inner svg: FAIL everywhere — no browser enforces the spec requirement that inner svg's currentTranslate is read-only - Chrome [SameObject]: Chrome returns a new SVGPoint object on each access (doesn't satisfy [SameObject]) See the following test [SVGSVGElement-currentTranslate.html](https://github.com/user-attachments/files/26816874/SVGSVGElement-currentTranslate.html) currently defined in https://w3c.github.io/svgwg/svg2-draft/struct.html#InterfaceSVGSVGElement See Also #360 --- If everyone agrees with the test I will add it to the WPT tests. See https://github.com/w3c/svgwg/issues/1094 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 April 2026 09:09:39 UTC