You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi Guys,
I am using Nextjs 12 with Google Maps. I am wondering if I can use the React-laag Popover element with a map marker.
I have managed to create the marker and on invoking an onClick function, the popover appears. But when panning the map, the popover element does not stay with the marker.
It is very possible that this is not a bug but merely the incorrect application of this utility.
Working Example is available at Codesandbox: Click Here
Expected behaviour
The Popover element should stick to the div element (for example the marker or button) when panning the maps.
Screenshots
Nextjs 12.2.0
React 18.3.0
Additional context
I have noticed weird behaviour with Markers and OverlayViews on React version 18. Not sure if it could be related.
To experience this behaviour, click on the map marker with-OverlayView and pan the map.
The text was updated successfully, but these errors were encountered:
Describe the bug
Hi Guys,
I am using Nextjs 12 with Google Maps. I am wondering if I can use the React-laag Popover element with a map marker.
I have managed to create the marker and on invoking an onClick function, the popover appears. But when panning the map, the popover element does not stay with the marker.
It is very possible that this is not a bug but merely the incorrect application of this utility.
Working Example is available at Codesandbox: Click Here
Expected behaviour
The Popover element should stick to the div element (for example the marker or button) when panning the maps.
Screenshots
Additional context
I have noticed weird behaviour with Markers and OverlayViews on React version 18. Not sure if it could be related.
To experience this behaviour, click on the map marker
with-OverlayView
and pan the map.The text was updated successfully, but these errors were encountered: