pointer-events not registered for elements using a clipPath with no fill

RESOLVED FIXED

Status

()

Core
SVG
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Doug Schepers, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(2 attachments, 1 obsolete attachment)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

Elements using clip-path should still receive pointer events.  If the element that they are clipping to (in the 'clipPath') has fill="none", then the pointer events do not seem to register on the clipped element.

Reproducible: Always

Steps to Reproduce:
1. In test file, click on the rectangles and circles 
2. an alert box identifying the clicked element should appear
3. 
Actual Results:  
rightmost circle, referencing the rect with no fill, does not fire an event

Expected Results:  
rightmost circle should fire an event

you might look at properties such as stroke, and also at style properties vs. presentation attributes
(Reporter)

Comment 1

10 years ago
Created attachment 261068 [details]
minimal test case

Comment 2

10 years ago
Created attachment 261071 [details] [diff] [review]
ignore pointer-events and early exit for clipPath children

Updated

10 years ago
Attachment #261071 - Flags: review?(longsonr)

Updated

10 years ago
Attachment #261071 - Flags: review?(longsonr) → review+

Updated

10 years ago
Attachment #261071 - Flags: superreview?(roc)
Comment on attachment 261071 [details] [diff] [review]
ignore pointer-events and early exit for clipPath children

+  // check if we're a clipPath - cheaper than IsClipChild(), and we shouldn't
+  // get in here for other nondisplay children

This sounds fragile. Can you at least assert that it's really a clippath?
Attachment #261071 - Flags: superreview?(roc) → superreview+

Comment 4

10 years ago
Please, consider bug 380053
What happened here?
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

10 years ago
Duplicate of this bug: 406624

Updated

10 years ago
Duplicate of this bug: 380053

Comment 8

10 years ago
(In reply to comment #5)
> What happened here?

Forgot to check in when it got reviews, then lost in the mists of time.

Comment 9

10 years ago
Created attachment 291286 [details] [diff] [review]
update to tip
Attachment #261071 - Attachment is obsolete: true
Attachment #291286 - Flags: superreview?(roc)
Attachment #291286 - Flags: review?(longsonr)

Updated

10 years ago
Attachment #291286 - Flags: review?(longsonr) → review+
Attachment #291286 - Flags: superreview?(roc) → superreview+

Updated

10 years ago
Attachment #291286 - Flags: approval1.9+

Comment 10

10 years ago
Checked in.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED

Comment 11

10 years ago
I'd like to reopen this bug for mac os x as this is broken
Jonathan, can you please file a new bug for the brokenness on Mac OS X and mark it as a dependency of this bug?

Comment 13

10 years ago
#11 files a separate bug:
Bug 407299 

Updated

10 years ago
Blocks: 407299
You need to log in before you can comment on or make changes to this bug.