How to disable map zoom when scrolling inside a scrollable child component?
See original GitHub issueHello,
Is there a way to disable map scrolling when you hover over a scrollable child component inside GoogleMapReact? I still would like to keep scrollwheel: true
for it to zoom on scroll when hovering on the map itself.
Thank you in advance.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Disable mouse scroll wheel zoom on embedded Google Maps
Show activity on this post. Here is a simple solution. Just set the pointer-events: none CSS to the <iframe> to disable mouse scroll....
Read more >How disable map zoom on scroll ? | WordPress.org
You need to go to Maps -> Settings -> Maps, the interaction options are there. Does that help? Kind regards – Perry. Thread...
Read more >Google Maps iframe embed disable scroll to zoom
Google Maps iframe embed disable scroll to zoom ... map can be done by using two fingers, as is prompted in the overlay...
Read more >Scroll - LVGL documentation
In LVGL scrolling works very intuitively: if an object is outside its parent content area (the size without padding), the parent becomes scrollable...
Read more >How to disable scrolling temporarily using JavaScript
In this method, a new CSS class is created where the height is set to 100%, and the scroll bar is disabled by...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You already answered on your question, you need to disable scrollwheel when you hovering on a child. All events exists in html 😃 scrollwheel disabled via options
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.