[svgwg] Issue: Remove un-implemented `pointer-events` "painted" rules for images marked as Scripting chapter

AmeliaBR has just labeled an issue for https://github.com/w3c/svgwg as "Scripting chapter":

== Remove un-implemented `pointer-events` "painted" rules for images ==
The [`pointer-events` definition](https://www.w3.org/TR/SVG2/interact.html#PointerEventsProp) contains detailed rules for "raster images" (presumably, any image embedded with `<image>`).  A key feature is that an image should only be considered "painted" in areas where it doesn't have full transparency.

There are two problems with this:

- it provides access to per-pixel image data without any requirements for cross-origin security restrictions
- none of the browser engines (as far as I can tell) implements it this way

Based on my testing [CodePen demo](https://codepen.io/AmeliaBR/pen/qjEKXe?editors=1100) browsers treat an `<image>` element as interactive over its full rectangular region, regardless of whether the image is same or cross-origin.







See https://github.com/w3c/svgwg/issues/322

Received on Monday, 5 June 2017 20:16:00 UTC