- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Jan 2019 16:18:53 +0000
- To: public-svg-issues@w3.org
@r12a What's missing is that Edge's behavior would be incorrect according to the proposed spec clarification. In that example, the Firefox behavior would be (mostly) correct: each code point gets assigned a new value from the attributes, but for actual layout grapheme clusters are laid out as one. If an author wanted the Edge rendering, they (or their authoring tool) would need to add extra placeholder values (`0` relative change for `dx`/`dy`, or a repeated absolute value for `x`/`y`) for the codepoints that don't represent independent layout characters. In general, the author is expected to position characters as makes the most sense for the language and design. The goal of the spec is to ensure the minimum possible discrepancy in renderings. Codepoints may not be the most intuitive, but they are unambiguous and will never change. (Unlike for example, newly introduced emoji clusters, which older browsers might not recognize as a single unit.) If the text rendering engine doesn't have a combined glyph for a character, the layout of those particular characters may be poor, but if all values are assigned by codepoint, then the remaining characters won't get shifted relative to the author's intent. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/537#issuecomment-453571126 using your GitHub account
Received on Friday, 11 January 2019 16:18:54 UTC