User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20070309 Firefox/184.108.40.206 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20070309 Firefox/18.104.22.168 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
Created attachment 261071 [details] [diff] [review] ignore pointer-events and early exit for clipPath children
Attachment #261071 - Flags: review?(longsonr) → review+
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+
Please, consider bug 380053
What happened here?
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #5) > What happened here? Forgot to check in when it got reviews, then lost in the mists of time.
Created attachment 291286 [details] [diff] [review] update to tip
Attachment #291286 - Flags: review?(longsonr) → review+
Attachment #291286 - Flags: superreview?(roc) → superreview+
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
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?
#11 files a separate bug: Bug 407299
You need to log in before you can comment on or make changes to this bug.