- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Nov 2018 21:13:12 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `SVGGeometry.prototype.isPointInStroke vs. vector-effects`, and agreed to the following: * ``RESOLUTION: vector-effects property contributes to hit-testing and `isPointInStroke`.`` <details><summary>The full IRC log of that discussion</summary> <AmeliaBR> Topic: SVGGeometry.prototype.isPointInStroke vs. vector-effects<br> <AmeliaBR> github: https://github.com/w3c/svgwg/issues/559<br> <SairusPatel> "Sairus & Dean at Adobe" should be: "Myles & Dean at Apple". I may have misspoken<br> <AmeliaBR> s/Sairus & Dean at Adobe/Myles & Dean at Apple/<br> <AmeliaBR> s/"Sairus & Dean at Adobe" should be: "Myles & Dean at Apple". I may have misspoken//<br> <AmeliaBR> Dirk: Question is whether vector-effect is just a visual effect or whether it actually affects geometry, and therefore hit-testing and the API.<br> <AmeliaBR> ... I'd like to get a resolution to adopt fsoder's recommendation: vector-effect should affect these APIs.<br> <AmeliaBR> Amelia: Agree that's ideal. Only concern was implementation cost, but I think browsers are already doing all the calculations so there shouldn't be much overhead.<br> <AmeliaBR> Dirk: I don't think there is any implementation concern.<br> <AmeliaBR> RESOLUTION: vector-effects property contributes to hit-testing and `isPointInStroke`.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/559#issuecomment-436036895 using your GitHub account
Received on Monday, 5 November 2018 21:13:13 UTC