You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Incorrect support data (ex. Chrome says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
All values for this property except non-scaling-stroke are considered as "at-risk", meaning they are not being developed by browser makers. See this document and search for the term "at risk": https://svgwg.org/svg2-draft/coords.html#issue31
I was able to verify this on Chrome 110.0.5481.177 but I believe there are a lot of browsers and versions that don't support the full property.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
As I already mentioned I think there are a lot of different browsers with different versions where this is a problem. W3C calls it a "lack of implementations". I would expect the compatibility table to either be adjusted completely to reflect reality properly or to have a disclaimer somewhere, e.g.:
Values other than non-scaling-stroke for the vector-effect attribute/property are currently at risk of being removed from the specification as they are not being developed by browser vendors.
(Adjusted from the note on Caniuse)
Did you test this? If so, how?
As mentioned, in Chrome 110.0.5481.177 by having a <text> element with vector-effect="non-scaling-size" inside a <g>, the size of which I changed using the transform property. I also had a rect in there to make sure my transforms were working. Both the rectangle and the text changed sizes but I was only expecting one of them to do so.
When I changed it to non-scaling-stroke (which is the only value that is broadly supported) it worked. The text still changed it's size but the stroke always remained the same thickness (e.g. very large text, but still 1px of stroke).
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
BCD does not have any data for values of vector-effect, and we don't record support data for a (sub-)feature until it is implemented in at least one browser.
What would be better in this case is to update the content and mark the values "at risk" accordingly, so I will transfer this issue to the content repo.
Josh-Cena
changed the title
svg.attributes.presentation.vector-effect - Incorrect compatibility data for at-risk values
Most vector-effect properties are at-risk
Jan 23, 2025
Josh-Cena
added
help wanted
If you know something about this topic, we would love your help!
and removed
needs triage
Triage needed by staff and/or partners. Automatically applied when an issue is opened.
labels
Jan 23, 2025
What type of issue is this?
Incorrect support data (ex. Chrome says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
All values for this property except
non-scaling-stroke
are considered as "at-risk", meaning they are not being developed by browser makers. See this document and search for the term "at risk": https://svgwg.org/svg2-draft/coords.html#issue31I was able to verify this on Chrome 110.0.5481.177 but I believe there are a lot of browsers and versions that don't support the full property.
Caniuse mentions it with a small note: https://caniuse.com/vector-effect
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
As I already mentioned I think there are a lot of different browsers with different versions where this is a problem. W3C calls it a "lack of implementations". I would expect the compatibility table to either be adjusted completely to reflect reality properly or to have a disclaimer somewhere, e.g.:
Values other than non-scaling-stroke for the vector-effect attribute/property are currently at risk of being removed from the specification as they are not being developed by browser vendors.
(Adjusted from the note on Caniuse)
Did you test this? If so, how?
As mentioned, in Chrome 110.0.5481.177 by having a
<text>
element withvector-effect="non-scaling-size"
inside a<g>
, the size of which I changed using thetransform
property. I also had arect
in there to make sure my transforms were working. Both the rectangle and the text changed sizes but I was only expecting one of them to do so.When I changed it to
non-scaling-stroke
(which is the only value that is broadly supported) it worked. The text still changed it's size but the stroke always remained the same thickness (e.g. very large text, but still 1px of stroke).Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/vector-effect
https://svgwg.org/svg2-draft/coords.html#issue31
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/vector-effect
MDN metadata
MDN page report details
svg.attributes.presentation.vector-effect
The text was updated successfully, but these errors were encountered: