- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Dec 2018 21:40:09 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `At-risk status of new stroke-linejoin keywords`, and agreed to the following: * `RESOLVED: Mark new stroke-linejoin keywords as at risk.` <details><summary>The full IRC log of that discussion</summary> <AmeliaBR> Topic: At-risk status of new stroke-linejoin keywords<br> <AmeliaBR> github: https://github.com/w3c/svgwg/issues/592<br> <AmeliaBR> Chris: These really do have to be at-risk. They are new features, and we have no browser implementations.<br> <AmeliaBR> Tav: There are implementations in Inkscape, using a modified version of Cairo. They are also recreated with our live path effects.<br> <AmeliaBR> Dirk: You said you implemented with Cairo?<br> <AmeliaBR> Tav: In a modified version. Not in the public library.<br> <AmeliaBR> ... we also have a similar thing in the path effects, which uses custom attributes that are then exported as standard SVG path. It's very popular among artists.<br> <AmeliaBR> Dirk: Any objections to marking at-risk?<br> <AmeliaBR> RESOLVED: Mark new stroke-linejoin keywords as at risk.<br> <AmeliaBR> Eric: Do we have any feedback from implementers? Is there any interest of implementing?<br> <AmeliaBR> Myles: Same issue as before. Not a lot of feedback from authors yet. I don't think there are technical obstacles.<br> <AmeliaBR> Chris: Again, I think we need more worked examples and education to get people excited about them.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/592#issuecomment-443880493 using your GitHub account
Received on Monday, 3 December 2018 21:40:11 UTC