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
At this point, WebKit, Blink and EdgeHTML support the baseline-shift property (some with bugs) for SVG text. Only Firefox doesn't support the baseline-shift property. Various non-browser UAs support baseline-shift on import as well.
On the other hand, there is no UA that supports vertical-align on SVG text. For that reason I'd like to ask to remove the issue from the spec and keep the baseline-shift property.
The text was updated successfully, but these errors were encountered:
@dirkschulze I think the issue is about the baseline value of baseline-shift, specifically. I'll clarify that in the issue wording. Lmk if you have any info on that question specifically? :)
There's an issue in that section about the baseline keyword, but there is also the following warning to authors:
Authors should use the vertical-align shorthand instead of this property.
Based on Dirk's comments, that warning should probably be modified to say “…except in SVG content.” (Or “legacy SVG content” or “SVG content for legacy user agents”.)
@dirkschulze I'm not entirely sure which issue you might have been referring to, would you mind taking a look and letting me know if your concerns are resolved?
Uh oh!
There was an error while loading. Please reload this page.
The spec has an open issue regarding support of
baseline-shift
: https://drafts.csswg.org/css-inline-3/#baseline-shift-propertyAt this point, WebKit, Blink and EdgeHTML support the
baseline-shift
property (some with bugs) for SVG text. Only Firefox doesn't support thebaseline-shift
property. Various non-browser UAs supportbaseline-shift
on import as well.On the other hand, there is no UA that supports
vertical-align
on SVG text. For that reason I'd like to ask to remove the issue from the spec and keep thebaseline-shift
property.The text was updated successfully, but these errors were encountered: