311942 - SVG <image> should honor pointer-events="painted" on transparent areas

Status: RESOLVED INVALID

(Core :: SVG, defect)

Description

[Bill Burdick]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

images with pointer-events="painted" should not receive mouse clicks in
transparent areas.  Here is a reference:
http://www.w3.org/TR/SVG/interact.html#PointerEventsProperty

Reproducible: Always

Steps to Reproduce:
1.open link (http://p2pmud.com/testsvg.html)
2.click in transparent area of green brain
Actual Results:  
click alert appears

Expected Results:  
click alert should only appear when you click on a nontransparent area of the brain.

NOTE: visiblePanted modifies this behavior to honor the 'visibility' property of
the image

Comment 1

[Bill Burdick]

Here's an update of the link: http://p2pmud.com/quarantine/testsvg.html

Comment 2

[Jonathan Watt [:jwatt]]

Bill, the <svg> tag in that testcase is not in the SVG namespace, so it's completely ignored. The <image> tag is therefore the HTML <image> tag. In other words, your testcase actually doesn't include any SVG, despite appearances.

Comment 3

[Bill Burdick]

I have made a pure svg test case which demonstrates the error: http://p2pmud.com/quarantine/tst.xml

Comment 4

[Robert Longson [:longsonr]]

Not yet implemented. There is a XXX reminder in the nsSVGImageFrame.cpp code for it.

Comment 5

[Jonathan Watt [:jwatt]]

Attachment: Bill's testcase

Comment 6

[Daniel Holbert [:dholbert]]

(In reply to comment #4)
> Not yet implemented. There is a XXX reminder in the nsSVGImageFrame.cpp code
> for it.

For convenience, here's the link to that in the code: http://tinyurl.com/3nuyfg

Comment 7

[Paul LeBeau]

An issue related to this bug is currently open in the spec issue tracker:

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

Comment 8

[Robert Longson [:longsonr]]

And per the latest update to https://github.com/w3c/svgwg/issues/322 we won't be doing this.