Skip to content
This repository has been archived by the owner. It is now read-only.

Manual editing of permalink in address bar broken #4945

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Manual editing of permalink in address bar broken #4945

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Reporter: MHohmann
[Submitted to the original trac issue database at 11.01am, Monday, 12th August 2013]

I'm using Firefox 23.0 on Ubuntu 12.04 and encountered the following problem:

  1. I navigate to http://www.openstreetmap.org and zoom into some area.
  2. In the address bar I get a permalink, say this one: http://www.openstreetmap.org/#map=8/58.898/25.587
  3. I switch to the traffic map and the link changes like this: http://www.openstreetmap.org/#map=8/58.898/25.587&layers=T
  4. I remove the "&layers=T" part in the adress bar and hit Enter, thus reproducing the permalink I had there before.
  5. I do not get to the previous view / Mapnik layer, but instead the traffic map stays and the "&layers=T" in the address bar reappears.

Alternative:
4. I change the "&layers=T" to "&layers=C" (permalink to the cycle map).
5. I do not get to the cycle map, but instead the traffic map stays. The "&layers=C" and the "&layers=T" in the address bar reappears as soon as I change the map area.

Expected behaviour: Entering a new permalink in the address bar should navigate to whatever that permalink describes.

Actual behaviour: Entering those permalinks has no effect and the changes in the address bar are reverted.

@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: TomH
[Added to the original trac issue at 2.19pm, Monday, 9th September 2013]

Fixed in [changeset:9bcd049/rails].

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant