| Summary: | Remove the SVG pathSegList interface | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Fredrik Söderquist <fs> |
| Component: | SVG | Assignee: | Karl Dubost <karlcow> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | ahmad.saleem792, annevk, ap, bfulgham, cdumez, heycam, karlcow, mmaxfield, rniwa, sabouhallawa, sam, webkit-bug-importer, zimmermann |
| Priority: | P2 | Keywords: | BrowserCompat, InRadar, WPTImpact |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://www.chromestatus.com/features/5708851034718208 | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=260894 | ||
| Bug Depends on: | 234227 | ||
| Bug Blocks: | 200143 | ||
|
Description
Fredrik Söderquist
2017-02-17 08:23:56 PST
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. 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! *** Bug 234041 has been marked as a duplicate of this bug. *** I think bug 260894 has a better title and clearer description for what is left to be done for SVGPathElement's. In fact in 2018 for firefox ttps://hg.mozilla.org/mozilla-central/diff/3e3cfa85d219e7d166f268474c1e38780e38be85/dom/webidl/SVGPathSeg.webidl Pull request: https://github.com/WebKit/WebKit/pull/24592 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 |