- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 May 2018 16:58:49 +0000
- To: public-svg-issues@w3.org
dirkschulze has just created a new issue for https://github.com/w3c/svgwg: == isPointInFill/isPointInStroke and display: none and other specifics == WebKit (in nightly) and Blink return `false` always for: `isPointInFill` * if `display: none` * (if `fill: none`) only on Blink * the element is _not_ attached to the current document context `isPointInStroke` * if `display: none` * if `stroke: none` * the element is _not_ attached to the current document context Both, webkit and blink, would not be able to compute `isPointIn*` for `display: none` or not-attached elements. This is an implementation detail that both engines can't easily work around. I believe Firefox has the same issue. CC @longsonr. For `stroke: none` and `fill: none` there probably is no implementation issue. At least on WebKit. We just need to decide if `none` values on `stroke` or `fill` will have an effect for the 2 methods. Spec text: https://svgwg.org/svg2-draft/types.html#InterfaceSVGGeometryElement Test case: https://codepen.io/krit/pen/VxEbdp Please view or discuss this issue at https://github.com/w3c/svgwg/issues/456 using your GitHub account
Received on Wednesday, 16 May 2018 16:58:52 UTC