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
When backdropEnabled is set to true on a SlidingUpPanel positioned above a GoogleMap widget, it blocks mouse interactions on the map, preventing users from dragging or interacting with it on Web.
To Reproduce
Add a GoogleMap widget.
Place a SlidingUpPanel widget above it. (using Stack)
Set backdropEnabled: true on the panel.
Attempt to drag or interact with the map in a web environment.
Expected Behavior:
Users should be able to interact with the Google Map widget behind the panel when backdrop is enabled, or have an option to disable the backdrop interaction block on Web.
Environment:
Platform: Web
Package version: Flutter 3.24.3
Browser and version: chrome v130
Note:
I spent quite a bit of time trying to figure this out, so I hope this helps others who might be dealing with the same issue!
The text was updated successfully, but these errors were encountered:
max-anders
changed the title
Widget lik not responding to mouse input on Flutter web due to bac
Backdrop Enabled Blocks Mouse Input on Underlying Google Map Widget (Web Only)
Nov 2, 2024
Describe the bug
When
backdropEnabled
is set totrue
on aSlidingUpPanel
positioned above aGoogleMap
widget, it blocks mouse interactions on the map, preventing users from dragging or interacting with it on Web.To Reproduce
Add a
GoogleMap
widget.Place a
SlidingUpPanel
widget above it. (using Stack)Set
backdropEnabled: true
on the panel.Attempt to drag or interact with the map in a web environment.
Expected Behavior:
Users should be able to interact with the Google Map widget behind the panel when backdrop is enabled, or have an option to disable the backdrop interaction block on Web.
Environment:
Note:
I spent quite a bit of time trying to figure this out, so I hope this helps others who might be dealing with the same issue!
The text was updated successfully, but these errors were encountered: