Add new spec: SVG Paths

[Elchi3]

URL

https://svgwg.org/specs/paths/

Rationale

Firefox apparently now ships (parts of) the SVG Path API: https://groups.google.com/a/mozilla.org/g/dev-platform/c/n5UXNSj5fTE

The spec comes with IDL that is now missing in webref -> therefore missing in the OWD BCD collector -> therefore missing in BCD for Firefox 137 beta :)

Additional properties

{}

[browser-specs-bot]

Changes to index.json

This update would trigger the following changes in index.json:

Add spec (1)

{
  "url": "https://svgwg.org/specs/paths/",
  "seriesComposition": "full",
  "shortname": "svg-paths",
  "series": {
    "shortname": "svg-paths",
    "currentSpecification": "svg-paths",
    "title": "SVG Paths",
    "shortTitle": "SVG Paths",
    "nightlyUrl": "https://svgwg.org/specs/paths/"
  },
  "organization": "W3C",
  "groups": [
    {
      "name": "SVG Working Group",
      "url": "https://www.w3.org/Graphics/SVG/WG/"
    }
  ],
  "nightly": {
    "url": "https://svgwg.org/specs/paths/",
    "status": "Editor's Draft",
    "alternateUrls": [],
    "repository": "https://github.com/w3c/svgwg",
    "sourcePath": "specs/paths/master/Overview.html",
    "filename": "Overview.html"
  },
  "title": "SVG Paths",
  "source": "spec",
  "shortTitle": "SVG Paths",
  "categories": [
    "browser"
  ],
  "standing": "good"
}

Tests

These changes look good! 😎

[tidoust]

That's interesting. We had kept this and other SVG specs out of the list on purpose based on the discussion in w3c/svgwg#824 which signaled the specs were essentially dead. I wonder why this hasn't been raised in the intent to prototype/ship.

In practice, I do not think anyone maintains the SVG Paths spec: it is not in scope of the SVG Working Group and the SVG Community Group has been dormant for some time now, to the point that svg-cg.org/ no longer works (source at https://github.com/svg-cg/svg-cg.github.io/). (Edit: I missed it, but the SVG Community Group was closed last year)

The Web IDL defined in the spec is slightly invalid: NoInterfaceObject should be LegacyNoInterfaceObject and there needs to be an Exposed somewhere. The spec also duplicates definitions that are defined in SVG 2, including the SVGPathElement interface. But then the spec does not follow the usual definitions data model.

[Elchi3]

Looks like https://searchfox.org/mozilla-central/source/dom/webidl/SVGPathElement.webidl is the IDL that is shipping and that appears to be correcting the issues you mentioned.

If this spec won't be considered for inclusion, let me know, as I can also add custom IDL to our collector project for it to be picked up. Happy to mark this as non-standard in BCD/on MDN for the moment.

[tidoust]

If there's support, let's add the spec. We'll add patches to fix the Web IDL.
The spec was published as a /TR spec a long time ago: https://www.w3.org/TR/svg-paths/. I'll use that as the canonical URL for the spec (with https://svgwg.org/specs/paths/ as nightly URL).

[tidoust]

Spec added. Will appear with next build. As said, a couple of patches will have to be added in Webref once the spec gets crawled.

[tidoust]

Looks like https://searchfox.org/mozilla-central/source/dom/webidl/SVGPathElement.webidl is the IDL that is shipping and that appears to be correcting the issues you mentioned.

Interestingly, that IDL is also invalid: the definition of the values attribute in SVGPathSegment is incorrect because attributes cannot accept sequence types. Anyway, I reported Web IDL issues in w3c/svgwg#967.