- From: Paul LeBeau <paul.lebeau@gmail.com>
- Date: Sat, 15 Aug 2015 08:52:34 +1200
- To: www-svg <www-svg@w3.org>
- Message-ID: <CACfsppC_iy_GcKLjfeUgKPQr2rONUGSnjCHgowWB=Rv_07i8Hg@mail.gmail.com>
Hi all I recently stumbled across this "oddity". Try the following link in Chrome. http://jsfiddle.net/u5z02hpx/8/ I would expect the vertical bar ('|') glyph to be vertical, but it is tilted. I initially thought it was a Chrome browser bug, as FF doesn't do it: But it turns out it is probably due to the following rule in the textPath layout instructions: When the inline-progression-direction > <http://www.w3.org/TR/SVG/text.html#SettingInlineProgressionDirection> is > horizontal, then any ‘x’ attributes on ‘text’ > <http://www.w3.org/TR/SVG/text.html#TextElement>, ‘tspan’ > <http://www.w3.org/TR/SVG/text.html#TSpanElement>, ‘tref’ > <http://www.w3.org/TR/SVG/text.html#TRefElement> or ‘altGlyph’ > <http://www.w3.org/TR/SVG/text.html#AltGlyphElement> elements represent > new absolute offsets along the path, thus providing explicit new values for > startpoint-on-the-path. That seems like an odd rule to me. Does anyone remember what the purpose of it was? It seems odd to complete override the startOffset calculation. Checking the main browsers, it looks like only IE has implemented the way it seems to be worded (x overrides startOffset). Chrome: startpoint-on-the-path = (startOffset + x) - wrong!? Firefox: startpoint-on-the-path = startOffset - wrong!? (seems to ignore it. x has no effect on startOffset) IE: startpoint-on-the-path = x - seems correct based on the wording. Paul
Received on Friday, 14 August 2015 20:53:24 UTC