Bug 168519 – Remove the SVG pathSegList interface

• Status: NEW
• Component: SVG

[Fredrik Söderquist]

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

[Sam Weinig]

Why was it removed? Why should we remove it?

[Said Abou-Hallawa]

(In reply to comment #1)
> Why was it removed? Why should we remove it?

Because there is a new intercase: https://svgwg.org/specs/paths/#InterfaceSVGPathSegment.

Here is the Chrome official bug: https://bugs.chromium.org/p/chromium/issues/detail?id=539385.

But this bug might be more interesting: https://codereview.chromium.org/1416273002.

[Ahmad Saleem]

I can find some references to it on Webkit Github mirror that "SVGPathSeg" is present:

https://github.com/WebKit/WebKit/search?l=C%2B%2B&q=pathSegList&type=code

I think only Safari is major browser supporting it as of right now:

https://caniuse.com/?search=PathSeg

but there is also highlight of the second bug from Chrome mentioned in Comment 02 being also merged into Webkit:

https://github.com/WebKit/WebKit/commit/8a435d350084afb918697abd44a3619bcb3bfae5

Is more worked required or caniuse needs to be updated? Thanks!

[Radar WebKit Bug Importer]

<rdar://problem/97100338>

[Ahmad Saleem]

*** Bug 234041 has been marked as a duplicate of this bug. ***

[Ahmad Saleem]

https://chromium.googlesource.com/chromium/src/+/240bb9316be42349d5185466ccf28f06f6eb8ee3

[Said Abou-Hallawa]

I think bug 260894 has a better title and clearer description for what is left to be done for SVGPathElement's.

[Karl Dubost]

See http://wpt.live/svg/historical.html
and http://wpt.fyi/svg/historical.html

[Karl Dubost]

Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=1631581

[Karl Dubost]

In fact in 2018 for firefox ttps://hg.mozilla.org/mozilla-central/diff/3e3cfa85d219e7d166f268474c1e38780e38be85/dom/webidl/SVGPathSeg.webidl

[Karl Dubost]

Pull request: https://github.com/WebKit/WebKit/pull/24592

[Karl Dubost]

Polyfill library created for the removal in Chrome.
https://github.com/progers/pathseg


The new draft has the Path data API, aka the d attribute, which is currently not implemented in WebKit.
https://svgwg.org/svg2-draft/paths.html#TheDProperty

I'm trying to determine if there are polyfill out there trying to map pathSeg to the d property and/or the opposite. 
This is Bug 234227