Chrome is inconsistent vs Firefox/Safari for onClick (and probably other) pointer events on custom shapes, requiring onPointerDown={(e)=>e.stopPropagation()} which is also not clearly documented.
How can we reproduce the bug?
Can be reproduced with any simple custom shape with this setup:
Set pointerEvents: all on a custom shape
Add a button with onClick={doSomething}
This works fine Safari/Firefox, but in Chrome you need to additionally add onPointerDown={(e)=>e.stopPropagation()} for it to work.
What browsers are you seeing the problem on?
Chrome
Contact Details
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
linear[bot]
commented
3 weeks ago
What happened?
Chrome is inconsistent vs Firefox/Safari for onClick (and probably other) pointer events on custom shapes, requiring
onPointerDown={(e)=>e.stopPropagation()}which is also not clearly documented.How can we reproduce the bug?
Can be reproduced with any simple custom shape with this setup:
pointerEvents: allon a custom shapeonClick={doSomething}This works fine Safari/Firefox, but in Chrome you need to additionally add
onPointerDown={(e)=>e.stopPropagation()}for it to work.What browsers are you seeing the problem on?
Chrome
Contact Details
No response
Code of Conduct