- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Oct 2018 15:33:17 +0000
- To: public-svg-issues@w3.org
I think it was definitely overlooked. >From an author perspective, the method is certainly less useful if it *doesn't* factor in `non-scaling-stroke`. While most of the other vector effects apply as transformations on the element as a whole (and therefore transform the definition of all points), a `non-scaling-stroke` doesn't affect the coordinates used for the element. So the question is: would it be burdensome for implementations to factor in `non-scaling-stroke` effects when calculating `isPointInStroke` ? > Extending this query to also include 'pathLength'. Not sure how you mean? In the sense that `pathLength` affects stroke dashing patterns, yes, it should affect `isPointInStroke`. Perhaps it would be more helpful if the [method definition](https://svgwg.org/svg2-draft/types.html#InterfaceSVGGeometryElement) simply referenced the [stroke-shape algorithm](https://svgwg.org/svg2-draft/painting.html#StrokeShape) instead of trying to enumerate the properties that affect the stroke. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/559#issuecomment-431403850 using your GitHub account
Received on Friday, 19 October 2018 15:33:23 UTC