Add support for "pointer-events: bounding-box"
Categories
(Core :: SVG, enhancement, P2)
Tracking
()
People
(Reporter: ed, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-needed, Whiteboard: [layout:backlog])
Updated•11 years ago
|
Comment 1•5 years ago
|
||
Support for this is now in Safari Tech Preview: https://webkit.org/blog/9658/release-notes-for-safari-technology-preview-96/
Comment 2•5 years ago
|
||
According to https://docs.w3cub.com/browser_support_tables/pointer-events/
"Chrome 65+ supports the bounding-box value."
Chrome 65 was released on March 6, 2018
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Is there any chance we can get this added to get rid of the webcompat issue for Firefox? Or what's holding us back in adding it given that all other major browsers have support now.
Comment 4•4 years ago
|
||
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #3)
Is there any chance we can get this added to get rid of the webcompat issue for Firefox? Or what's holding us back in adding it given that all other major browsers have support now.
I'll add it to our backlog. I don't think anything is holding us back other than prioritization. Is it blocking important automation work?
heycam: Any reason not to do this?
Comment 5•4 years ago
|
||
For automation we have the workaround to click an actual element from within the group to trigger the click, and I assume that empty groups won't exist anyway.
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Hi Jonathan, I would like to ask if there has been any changes in priority and if we still want to have this feature. It would be great to have for WebDriver. Thanks.
Comment 8•2 years ago
|
||
We could certainly bump this up to get it on the radar. Layout is planning on doing some SVG work in H1 next year.
Is this needed as part of some MoCo/MoFo work?
Comment 9•2 years ago
|
||
(In reply to Jonathan Watt [:jwatt] from comment #8)
We could certainly bump this up to get it on the radar. Layout is planning on doing some SVG work in H1 next year.
Thanks for considering.
Is this needed as part of some MoCo/MoFo work?
No we don't require it. It would only be a nice thing to get bug 1668488 fixed. But users should be able to live with the workaround.
Updated•1 year ago
|
Description
•