Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Canvas renderer obscure other interactive overlays
See original GitHub issueA side effect of #3946.
If a vector feature rendered in a <canvas> is partially overlapping some other overlay layer (e.g. an image overlay), then the canvas will capture all events, and will take precedence when it comes to the mouse pointer (i.e. mouse pointer doesn’t change to the “hand with finger” when hovering the partially overlapped overlay).
Wondering about the real impact of this, given that nowadays the SVG renderer is supported in all major browsers and canvas is seldom used.
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve just run into this one. Canvas gives a nice performance boost over SVG when rendering lots of layers. Unfortunately, this kills the ability to stack/prioritize panes using zIndex while maintaining mouse interaction. The SVG renderer can cripple the browser really quickly which makes the map useless.
Any plans to fix this ? I am using 1.3.1 and mouse events are not propagated if the canvas pane z-index is bigger, even outside the layers of the canvas. As described in #4378