Closed Bug 1340572 Opened 7 years ago Closed 2 years ago

Remove the SVG pathSegList interface

Categories

(Core :: SVG, task, P3)

task

Tracking

()

RESOLVED DUPLICATE of bug 1388931

People

(Reporter: fsoder, Unassigned)

Details

(Keywords: dev-doc-needed, site-compat)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2950.4 Safari/537.36 OPR/44.0.2487.0 (Edition developer)

Steps to reproduce:

This interface, and the associated SVGPathSeg* was removed in Chromium in version 48.

https://www.chromestatus.com/features/5708851034718208
What's the standards status of this?  What are authors expected to use instead, and do we implement it?
Flags: needinfo?(cam)
We have not implemented the alternative (https://svgwg.org/specs/paths/#InterfaceSVGPathData). 

I don't think we should remove this interface till we have.
SVGPathSegList provided authors two things:

1. A way to get/modify/insert/delete individual commands within a <path d=""> attribute using a live, list-like DOM interface.

2. A way to get a normalized view of the path data (though we never implemented that; bug 446654).

Chrome has a bug filed to implement the proposed alternative, though in that bug there are a few comments from web developers asking for the old one back:

https://bugs.chromium.org/p/chromium/issues/detail?id=545467

Philip Rogers wrote a polyfill for the old API, FWIW:

https://github.com/progers/pathseg
Flags: needinfo?(cam)
Priority: -- → P3
Type: defect → task
Keywords: site-compat

Firefox 97.0, SVGPathSegList disappeared, many of my pages broken, no alternative API provided.
Do you thing that this is the right way to provide new releases of the browser?

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Resolution: FIXED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.