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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
(where 53.1221, -1.4816, zoom 16 is the location that I was last viewing the map on this browser before viewing the note page)
What used to happen was that the area around the note was shown in the editor. The note itself wasn't (which is arguably an omission, but that's an entirely separate issue)
For info the "edit area" link on the browse note page goes to:
Author: jfire [Added to the original trac issue at 6.12pm, Friday, 16th August 2013]
I suspect this never worked correctly. I tested as far back as 3880ac5d (July 19) -- prior to any of the map UI or permalink changes -- and neither P2 nor iD go to the note's location.
Reporter: SomeoneElse
[Submitted to the original trac issue database at 2.08pm, Friday, 16th August 2013]
I noticed this on this page:
http://www.openstreetmap.org/browse/note/10974
(I typed that into the address bar)
The "edit note" link shows up in the browser as:
http://www.openstreetmap.org/edit?note=10974
If I click that I'm taken to that link initially but then some sort of redirect occurs to
http://www.openstreetmap.org/edit?note=10974#map=16/53.1221/-1.4816
My default editor is P2.
(where 53.1221, -1.4816, zoom 16 is the location that I was last viewing the map on this browser before viewing the note page)
What used to happen was that the area around the note was shown in the editor. The note itself wasn't (which is arguably an omission, but that's an entirely separate issue)
For info the "edit area" link on the browse note page goes to:
http://www.openstreetmap.org/edit?bbox=-0.0419926643371582%2C51.58986944418806%2C-0.030319690704345707%2C51.5951750150238
which works as expected.
The browser is Firefox 22.0 on Windows 7.
The text was updated successfully, but these errors were encountered: