[svgwg] New Interface SVGPathSegment: segments should be more editable (#974)

herrstrietzel has just created a new issue for https://github.com/w3c/svgwg:

== New Interface SVGPathSegment: segments should be more editable ==
When @longsonr informed me on StackOverflow that Firefox started to implement the pathData interface methods I stumpled upon the current not fully editable concept `SVGPathSegment` object. 

I wasn't sure if the current "read-only" state of [`SVGPathSegment`](https://svgwg.org/specs/paths/#InterfaceSVGPathSegment) was just due to the rather new implementation but it seems that this concept is actually intended by the specs as pointed out by 
**@lovasoa's issue report**. ("Clarification on [NoInterfaceObject] for SVGPathSegment and Usage of setPathData()")https://svgwg.org/specs/paths/#InterfaceSVGPathSegment

OK we can do some basic stuff as command coordinate rounding. But we can't create pathData from scratch.

I hope I'm just missing a point.   

If not: the whole idea of a standard/native browser parsing method is rather pointless if we can't fully manipulate the pathData including methods to:  
* add/remove Segments
* create pathData segments from scatch

While it's perfectly clear the native methods are not intended to replace a full-blown SVG-library we should be able to manipulate segments otherwise the concept of `setpathData()` is pointless – `getPathData()` would still be useful.  

In other words: maybe this is the right time to tweak the specs.


Please view or discuss this issue at https://github.com/w3c/svgwg/issues/974 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 5 April 2025 01:49:31 UTC