Re: [w3c/editing] Clarification on [NoInterfaceObject] for SVGPathSegment and Usage of setPathData() (Issue #483)

viralipurbey left a comment (w3c/editing#483)

This issue has been resolved by the SVG WG.

At the March 26, 2026 SVG WG telecon (https://www.w3.org/2026/03/26-svg-minutes.html), the WG reached a formal resolution to change `SVGPathSegment` from a `[NoInterfaceObject]` interface to a dictionary, which is exactly what was proposed here:
 
```
dictionary SVGPathSegment {
    required DOMString type;
    required sequence<unrestricted float> values;
};
```

With this change, `setPathData()` natively accepts plain `{type, values}` JavaScript objects, no special instantiation required.
 
Relevant links:

- SVG WG resolution discussion: w3c/svgwg#1082
- Constructability discussion (also resolved): w3c/svgwg#974
- Spec PR implementing the change: w3c/svgwg#1106
- Firefox POJO fix (shipped in Firefox 138): https://bugzilla.mozilla.org/show_bug.cgi?id=1934525
 
Since this is resolved on the SVG WG side with a spec PR in progress, I believe we can close this issue. Thank you @lovasoa for raising it, it helped drive the spec update.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/483#issuecomment-4428595545
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/483/4428595545@github.com>