-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
map does not render or renders only once, then snap back to Lampenhain #392
Comments
@dvodvo Thanks for reporting. I transferred this issue to our maps client repository. |
I have tried to reproduce the problem after a system re-start. Therefore - as Firefox was involved in both cases - I have to assume it is a memory management problem of Firefox and not the maps client per se. I leave the final judgement as to closing this issue to you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Problem description
Issue with web application https://maps.openrouteservice.org/
both on Mac OS X 12.3 running Firefox 116.0
and
firefox Focus 109.1.1 running on Android 9
I load a GPX file.
It renders in the browser window.
But then I click anything (here, for example, I changed to view to a topographical one) and the map returns to Lampenhain, which sort of defeats the purpose... Certainly zooming (also tested and returning the same behaviour) is 99% required.
On can note that some of the data from the file import remains in the side pane.
• on OSX only a single point remains (as above)
• on android all points of GPX data are in the side bar, but the map reverted to Hilsenhain / Lampenhain.
Subsequently, I can attempt to reload a file, but the map stays at Hilsenhain / Lampenhain.
Even though the data is apparently loaded
Proposed solution
The map should be maintained and cleared only once the button to clear has been activeated or a new file loaded.
Additional context
No response
Forum Topic Link
No response
The text was updated successfully, but these errors were encountered: