- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Sep 2024 00:38:59 +0000
- To: public-svg-issues@w3.org
It looks like that was my proposal and from what I can tell it was [discussed at the 2013 Tokyo F2F](https://www.w3.org/2013/06/03-svg-minutes.html#item19). I then [updated the proposal in Septmber](https://lists.w3.org/Archives/Public/www-svg/2013Sep/0029.html). I don't know if it was ever discussed after that. (I notice the polyfill is broken too because we deprecated several SVG path APIs.) I think since that point browsers have been investing less in new SVG features for various reasons. I believe I might also have received feedback offline that adding primitives not natively supported by underlying graphics libraries would be a significant hurdle for many implementations. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/svgwg/issues/953#issuecomment-2332965150 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 September 2024 00:39:00 UTC