- From: Boris Dalstein via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Dec 2019 16:23:36 +0000
- To: public-svg-issues@w3.org
In this case however, we could also argue that this attribute is more than just a fix, but are legitimate separate policies that authors may want to choose from. For example, since currently the only available policy is "openpath", it is absolutely impossible to avoid duplicated markers on filled shapes with holes (see my example above). A different policy (subpaths) is what would work in this use case. However, I could also see use cases where it is useful to have a marker-start/end only at the start/end of the path, not at each subpath. For example for some kind of partially-visible arrow, where you want to control more precisely using subpaths which part of the arrow is visible, in way which wouldn't be possible with dashing. So these different policies are actually independently useful, easy to implement, and hard or impossible to simulate/workaround via other means (especially if you want to animate the content). These policies could have in fact be proposed directly for SVG 1: they're not just a "version-like tag" to fix a broken behavior while preserving backward compatibility. -- GitHub Notification of comment by dalboris Please view or discuss this issue at https://github.com/w3c/svgwg/issues/753#issuecomment-561720381 using your GitHub account
Received on Wednesday, 4 December 2019 16:23:37 UTC