inconsistent baseline key in svg presentation attributes

[skyclouds2001]

alignment-baseline
https://drafts.csswg.org/css-inline/#propdef-alignment-baseline
https://svgwg.org/svg2-draft/text.html#AlignmentBaselineProperty

baseline-shift
https://drafts.csswg.org/css-inline/#propdef-baseline-shift
https://svgwg.org/svg2-draft/text.html#BaselineShiftProperty

color-interpolation-filters
https://drafts.fxtf.org/filter-effects/#ColorInterpolationFiltersProperty

direction
https://drafts.csswg.org/css-writing-modes/#propdef-direction
https://svgwg.org/svg2-draft/text.html#DirectionProperty

dominant-baseline
https://drafts.csswg.org/css-inline/#propdef-dominant-baseline
https://svgwg.org/svg2-draft/text.html#DominantBaselineProperty

image-rendering
https://drafts.csswg.org/css-images/#propdef-image-rendering
https://svgwg.org/svg2-draft/painting.html#ImageRenderingProperty

lighting-color
https://drafts.fxtf.org/filter-effects/#LightingColorProperty

text-decoration
https://svgwg.org/svg2-draft/text.html#TextDecorationProperties
https://drafts.csswg.org/css-text-decor/#propdef-text-decoration

[ddbeck]

Hi @skyclouds2001. I don't understand the issue here. It's not clear to me what these specification links mean.

Can you describe what you expected to find in the data and what you actually found in the data? Can you tell us how it negatively affected your use of the data?

[skyclouds2001]

For example, svg.global_attributes.text-decoration is of svg group, while css.properties.text-decoration is of text-decoration group. I think svg.global_attributes.text-decoration should also be text-decoration group.

And css.properties.lighting-color is of svg-filters group, while svg.global_attributes.lighting-color is of svg group. I think svg.global_attributes.lighting-color should also be svg group.

This occurs the same as other svg presetation attributes

[ddbeck]

Thanks for filing the issue and thanks for your patience while I came back to it. I think this is broadly intentional, though it's possible this could change if #1173 is resolved.

When we created the features, we arrived at a compromise to handle the likely case that a developer who wishes to use a particular CSS property is typically unlikely to require the corresponding SVG attribute (if it exists). This is why we grouped most attributes with the SVG feature. That said, we did leave open the door for splitting the SVG feature into smaller features, if someone had a use case for such a thing.

Without a description of a negative impact (i.e., some application for web-features data that cannot be fulfilled due to the assignment of keys), I don't expect this to change at this time—but if you have a specific scenario, then feel free to file a new bug. Thanks for your understanding.