- From: Jon Ferraiolo via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Aug 2018 04:49:01 +0000
- To: public-svg-issues@w3.org
My opinion: drop everything but non scaling stroke. Lighten the burden on user agents, authoring tools, converters, book authors, students, and the WG itself. Keep it simple. In fact, I would not cry if the entire feature were dropped. If this set of functionality can't be achieved easily in Javascript, then better to add better DOM APIs into the spec and/or write a how-to blog post than add automagic features used only a tiny fraction of language users. Note that I have had a requirement for a non scaling stroke with SVG1 and found that I could achieve the desired result if I organized my transformations in the right way. It was not difficult. -- GitHub Notification of comment by JonFerraiolo Please view or discuss this issue at https://github.com/w3c/svgwg/issues/306#issuecomment-411635524 using your GitHub account
Received on Thursday, 9 August 2018 04:49:36 UTC