W3C home > Mailing lists > Public > public-svg-issues@w3.org > November 2018

Re: [svgwg] SVGGeometry.prototype.isPointInStroke vs. vector-effects

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
Message-ID: <issue_comment.created-436036895-1541452391-sysbot+gh@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>
&lt;AmeliaBR> Topic: SVGGeometry.prototype.isPointInStroke vs. vector-effects<br>
&lt;AmeliaBR> github: https://github.com/w3c/svgwg/issues/559<br>
&lt;SairusPatel> "Sairus &amp; Dean at Adobe" should be: "Myles &amp; Dean at Apple". I may have misspoken<br>
&lt;AmeliaBR> s/Sairus &amp; Dean at Adobe/Myles &amp; Dean at Apple/<br>
&lt;AmeliaBR> s/"Sairus &amp; Dean at Adobe" should be: "Myles &amp; Dean at Apple". I may have misspoken//<br>
&lt;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>
&lt;AmeliaBR> ... I'd like to get a resolution to adopt fsoder's recommendation: vector-effect should affect these APIs.<br>
&lt;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>
&lt;AmeliaBR> Dirk: I don't think there is any implementation concern.<br>
&lt;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

This archive was generated by hypermail 2.3.1 : Monday, 5 November 2018 21:13:14 UTC