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
Interacting with the filter container or the search container also registers as interacting with the map, which can lead to the map changing when the user does not intend for it to. For example, if you were selecting and deselecting a filter quickly, the map would register as a double click and it would zoom to a region of the map. This is especially annoying on mobile.
This could be a blunt fix (disable map movement when the search or filter is open) or a fix with a bit more finesse (clicking on the search/filter UI does not register on the map (e.preventDefault??)) (These are just some ideas, it may take a bit more research to figure out the exact right approach!)
The text was updated successfully, but these errors were encountered:
I' d like to be assigned to this issue. I put Filterand Search component out of the MapContainer. and the double click in those components don't zoom the map anymore. I'd love to test more and make a pull request.
Interacting with the filter container or the search container also registers as interacting with the map, which can lead to the map changing when the user does not intend for it to. For example, if you were selecting and deselecting a filter quickly, the map would register as a double click and it would zoom to a region of the map. This is especially annoying on mobile.
This could be a blunt fix (disable map movement when the search or filter is open) or a fix with a bit more finesse (clicking on the search/filter UI does not register on the map (e.preventDefault??)) (These are just some ideas, it may take a bit more research to figure out the exact right approach!)
The text was updated successfully, but these errors were encountered: