Re: [svgwg] Why most of SVG 2 properties are not presentational? (#900)

I would understand differentiation between something like `width` and `fill`. In that case the latter is obviously just a style.
The problem is that SVG 1 had no such separation and SVG 2 suddenly has.
Moreover, SVG 2 allows `width` to be a "style" property now. Which doesn't make any sense.

In SVG 2, you basically write XML as `<rect style="..."/>`, which is absurd, because XML already has a syntax for individual properties.

Also, it's completely inconsistent. Especially for text properties. `font-family="Arial"` is fine, but `font-kerning="none"` isn't.  Try explaining that to a user...

>However, currently, there seems to be no relevant activity, that SVG 2 will ever become a recommendation anyway

Are you sure? Browsers actively implementing it. It's already marked as _Candidate Recommendation_. And more and more people and tools rely on SVG 2 features. 
As an SVG library author I cannot simply ignore SVG 2 just because it's not a _true_ standard yet.

-- 
GitHub Notification of comment by RazrFalcon
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/900#issuecomment-1321820398 using your GitHub account


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

Received on Monday, 21 November 2022 10:17:24 UTC