- From: Mikael Sand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Aug 2017 01:17:14 +0000
- To: public-svg-issues@w3.org
@fsoder This is more about the fact the what the browsers implement (de-facto web standard) and what the SVG specification language specifies are different. Only Edge implements the spec correctly and with some (perhaps?) unexpected results. So I'm now thinking, would be best to define the current de-facto standard web browser behaviour as the default? And then, the specification standard as the optional one. Thus, if browsers actually want to implement and make available the standard SVG 1.1 text on a path algorithm (and SVG 2.0), and conform the same way as Edge, then they can choose to expose the new attribute, to enable triggering the non-default, but correct behaviour. -- GitHub Notification of comment by msand Please view or discuss this issue at https://github.com/w3c/svgwg/issues/337#issuecomment-325526331 using your GitHub account
Received on Tuesday, 29 August 2017 01:17:11 UTC