[w3ctag/design-reviews] Other Spec Review: SVG Path Data API: getPathData(), setPathData(), getPathSegmentAtLength() (Issue #1292)

SteveBeckerMSFT created an issue (w3ctag/design-reviews#1292)

### Specification

https://w3c.github.io/svgwg/specs/paths/#InterfaceSVGPathData

### Explainer

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SVG/SVGPathDataAPI/explainer.md

### Links

- Previous early design review, if any: N/A
- An introduction to the feature, aimed at unfamiliar audiences: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SVG/SVGPathDataAPI/explainer.md#introduction
- A description of the problems that end-users were facing before this proposal: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SVG/SVGPathDataAPI/explainer.md#user-facing-problem
- Alternatives considered: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SVG/SVGPathDataAPI/explainer.md#alternatives-considered
- Examples of how to use the proposal to solve the end-users' problems: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SVG/SVGPathDataAPI/explainer.md#proposed-approach
- What do the end-users experience with this proposal: N/A
- User research you did to validate the problem and/or design, if any: N/A
- Web Platform Tests:  https://wpt.fyi/results/svg/path/interfaces?label=experimental&label=master&aligned


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/w3c/svgwg/
- Primary contacts: 
  - @SteveBeckerMSFT, Microsoft
  - @dirkschulze, Adobe
- Organization/project driving the specification: Microsoft
- This work is being funded by: Microsoft, Google, Mozilla
- Primary standards group developing this feature: W3C SVG WG
- Incubation and standards groups that have discussed the design:
  - https://github.com/w3c/svgwg/issues/964
  - https://github.com/w3c/svgwg/issues/974
  - https://github.com/w3c/svgwg/issues/1082


### Feedback so far

- Multi-stakeholder feedback:
  - Chromium comments: Positive with 45 votes on the [issue](https://issues.chromium.org/issues/40441025).
  - Mozilla comments: Positive.  Shipped in Firefox 137 in April 2025.
  - WebKit comments: TBD
- Major unresolved issues with or opposition to this specification: None.
- Status/issue trackers for implementations: 
  - https://bugzilla.mozilla.org/show_bug.cgi?id=1934525
  - https://issues.chromium.org/issues/40441025
  - TBD
 

### You should also know that...

There's discussion in the working group to extend these APIs to animated values:

https://github.com/w3c/svgwg/issues/1197

There's also discussion to further enhance getPathSegmentAtLength():

https://github.com/w3c/svgwg/issues/1186

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1292


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1292
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1292@github.com>