So I can stop groaning when I accidentally trigger the drop-down menu while panning around ![]()
Yeah, this seems like a very useful prompt. Thanks!
Relatedly, I just came across this tweet:
It’s surprising to me that “Menus opening on hover, not tap/click” is a frustration, but your example does directly highlight how it can be a pain.
It would be interesting to see what kind of traction a “Change the menus from opening on hover to opening on tap/click” #ideas would get…
Update: Let’s find out
Change the menus from opening on hover to opening on tap/click
Hey @JamesChevalier are we getting this in the next update? I just screwed up a route again by triggering the drop-down menu accidentally and it reminded me of this post… 
I’m going through the Ideas category & came across this … The back button in your browser should resolve this - I’ve built the map in a way that allows you to use Route Builder throughout the site without losing anything.
For example, start building a route on an activity page and then navigate to your profile and then to a city page - everything about Route Builder should still be present and ready for you to continue building your route.
I prefer this capability over blocking/scaring someone into thinking they can’t leave the page they’re on while using Route Builder.
Yep! Been all good now for years ![]()