[svgwg] Properties defined in other CSS specifications (#861)

tidoust has just created a new issue for https://github.com/w3c/svgwg:

== Properties defined in other CSS specifications ==
As part of crawling specs and releasing the [@webref/css](https://www.npmjs.com/package/@webref/css) npm package which contains a list of CSS property definitions scraped from published specs, I have been looking at guarantees that the package could provide. A guarantee that seems sane is **"each property has one and only one definition"**. That is unfortunately not the case yet (see https://github.com/w3c/webref/issues/127#issuecomment-874135280 for a full list).

Focusing on SVG-related properties, I see that all properties defined in [svg-strokes](https://svgwg.org/specs/strokes/) are also defined in [fill-stroke-3](https://drafts.fxtf.org/fill-stroke/). I am not clear which definitions should be viewed as the "correct" ones (if there exists a "correct" definition today) and I am not clear whether there exists a grand scheme to converge to a situation where properties are defined only once. Is fill-sroke-3 meant to replace SVG strokes? Also, is this mentioned/tracked somewhere?

The properties in question are:
- `stroke-dasharray` 
- `stroke-dashoffset`
- `stroke-linecap`
- `stroke-linejoin`
- `stroke-miterlimit`
- `stroke-opacity`
- `stroke-width`
- `stroke`

I note that these same properties are also defined in SVG 2.

The SVG 2 spec also includes definitions for SVG 2 properties that are also defined elsewhere:
- `fill-opacity` also defined in [fill-stroke-3](https://drafts.fxtf.org/fill-stroke/)
- `fill-rule` also defined in [fill-stroke-3](https://drafts.fxtf.org/fill-stroke/)
- `fill` also defined in [fill-stroke-3](https://drafts.fxtf.org/fill-stroke/)
- `image-rendering` also defined in [css-images-3](https://drafts.csswg.org/css-images-3/)
- `inline-size` also defined in [css-logical-1](https://drafts.csswg.org/css-logical-1/)
- `shape-inside` also defined in [css-round-display-1](https://drafts.csswg.org/css-round-display/), [css-shapes-2](https://drafts.csswg.org/css-shapes-2/)
- `shape-margin` also defined in [css-shapes-1](https://drafts.csswg.org/css-shapes/)

Same questions there. Is the plan for CSS specs to be the "source of truth"? And is this tracked somewhere?

If the plan is to drop property definitions from SVG in favor of definitions in CSS specs, are there gotchas to proceeding with the plan? For instance, do definitions in CSS specs need to be completed first? Or could someone who is not too well-versed in SVG help with that through PRs that replace definitions with references to the right CSS specs?

Please view or discuss this issue at https://github.com/w3c/svgwg/issues/861 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 8 July 2021 12:54:05 UTC