This interface, and the associated SVGPathSeg* was removed in Chromium in version 48.
Why was it removed? Why should we remove it?
(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.