Details

Steps to reproduce

I’ve made a small example to demonstrate how Edge is the only browser implementing the SVG spec correctly, regarding calculating the glyph position relative to the glyph-midline.

The SVG 1.1 and 2.0 specification says:
Position the glyph such that the glyph-midline passes through the midpoint-on-the-path and is perpendicular to the line through the startpoint-on-the-path and the endpoint-on-the-path.

And a note after the list:
In the calculations above, if either the startpoint-on-the-path or the endpoint-on-the-path is off the end of the path, then extend the path beyond its end points with a straight line that is parallel to the tangent at the path at its end point so that the midpoint-on-the-path can still be calculated.

I suggest, that Edge makes the de-facto web standard (and much more efficient in both computation and memory) implementation available by default, and the conformant algorithm behind an attribute with some appropriate name and values, which would be added to the SVG 2.0 draft.

What are your thoughts on this?
Is the behavior that all existing text on a path svg content on the web has been designed against and the fact that it works the same way as when it was authored or not, more important?
Or is spec conformance more important?
Should a compatibility attribute be added?

Attachments

1 attachment

Comments and activity

I suggest we continue discussion of this in the SVG wg github repo issue, as I don’t really use the email which this account is bound to, and might not notice when replies are made. I also suggest a discussion between the various browser vendors/teams to reach a consensus regarding how to resolve this.

Suggesting a root cause

Help make the web just work! Identifying a root cause helps us resolve issues more quickly. If you have a theory for the root cause or have identified and reduced a reproducible bug, include a description and any relevant code or URLs in your comment and mark it as a root cause suggestion. Our engineers will take a look and update the bug with the results of our investigation.