168519 2017-02-17 08:23:56 -0800 Remove the SVG pathSegList interface 2024-02-16 10:06:12 -0800 1 1 1 Unclassified WebKit SVG WebKit Nightly Build Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=260894 https://www.chromestatus.com/features/5708851034718208 BrowserCompat, InRadar, WPTImpact P2 Normal --- 234227 200143 1 fs karlcow ahmad.saleem792 annevk ap bfulgham cdumez heycam karlcow mmaxfield rniwa sabouhallawa sam webkit-bug-importer zimmermann oldest_to_newest 1278268 0 fs 2017-02-17 08:23:56 -0800 This interface, and the associated SVGPathSeg* was removed in Chromium in version 48. 1279457 1 sam 2017-02-21 11:47:23 -0800 Why was it removed? Why should we remove it? 1279509 2 sabouhallawa 2017-02-21 13:44:33 -0800 (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. 1883682 3 ahmad.saleem792 2022-07-14 11:11:51 -0700 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! 1884390 4 webkit-bug-importer 2022-07-15 16:32:24 -0700 <rdar://problem/97100338> 1973813 5 ahmad.saleem792 2023-08-27 03:15:48 -0700 *** Bug 234041 has been marked as a duplicate of this bug. *** 1974560 6 ahmad.saleem792 2023-08-30 16:02:02 -0700 https://chromium.googlesource.com/chromium/src/+/240bb9316be42349d5185466ccf28f06f6eb8ee3 1974571 7 sabouhallawa 2023-08-30 16:37:08 -0700 I think bug 260894 has a better title and clearer description for what is left to be done for SVGPathElement's. 2014356 8 karlcow 2024-02-15 23:02:07 -0800 See http://wpt.live/svg/historical.html and http://wpt.fyi/svg/historical.html 2014357 9 karlcow 2024-02-15 23:04:18 -0800 Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=1631581 2014358 10 karlcow 2024-02-15 23:09:53 -0800 In fact in 2018 for firefox ttps://hg.mozilla.org/mozilla-central/diff/3e3cfa85d219e7d166f268474c1e38780e38be85/dom/webidl/SVGPathSeg.webidl 2014360 11 karlcow 2024-02-15 23:11:51 -0800 Pull request: https://github.com/WebKit/WebKit/pull/24592 2014537 12 karlcow 2024-02-16 10:06:12 -0800 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