Re: [svgwg] Clarify relation of isPointInFill and pointer-events

I *think* the idea was that the `isPointIn*` methods were supposed to respect clipping applied to the shape like `pointer-events` do. Furthermore, this was probably easier to describe than redefining which winding rule to use when? (`clip-rule` when the shape is child of `<clipPath>` and `fill-rule` otherwise.)

However, then again, hit testing on a shape within a `<clipPath>` can't happen anyway so would those methods return `false` all the time?

Also, should it matter if `visibility` is applied on a shape or not?

I would prefer that those functions operate as independent of any context as possible. Independent where they are and independent if they get clipped or not. However, what about the winding rule? Require an additional argument for the winding rule instead of magically chose `clip-rule` over `fill-rule`?

-- 
GitHub Notification of comment by dirkschulze
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/416#issuecomment-383266128 using your GitHub account

Received on Saturday, 21 April 2018 04:08:50 UTC