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
If one searches on Android in the website, for like a town, one gets the town centred in view.
There is a large overlay, by which one can even see its boundaries.
But when one closes that overlay by the cross, the centring is lost by something like 10 kilometres to the south-west!
I don't even understand what and why this happens.
Anyway, this is completely annoying , as one has to zoom out, and manually look for the town one already had in view!
So please recentre to the found item after closing the overlay.
By the way, showing search history is more useful to the average user than mapping history, which is present by a large button right under the search entry. Confusing too.
Screenshot(s) or anything else?
No response
The text was updated successfully, but these errors were encountered:
There are many existing complaints about the map moving when the sidebar is opened/closed so this is probably a duplicate but the code is basically incomprehensible and nobody dares touch it I'm afraid :-(
URL
No response
How to reproduce the issue?
If one searches on Android in the website, for like a town, one gets the town centred in view.
There is a large overlay, by which one can even see its boundaries.
But when one closes that overlay by the cross, the centring is lost by something like 10 kilometres to the south-west!
I don't even understand what and why this happens.
Anyway, this is completely annoying , as one has to zoom out, and manually look for the town one already had in view!
So please recentre to the found item after closing the overlay.
By the way, showing search history is more useful to the average user than mapping history, which is present by a large button right under the search entry. Confusing too.
Screenshot(s) or anything else?
No response
The text was updated successfully, but these errors were encountered: