Opened 5 years ago

Last modified 5 years ago

#4948 new enhancement

"Share/HTML" unexpectedly leaves away some highlight features

Reported by: aseerel4c26 Owned by: rails-dev@…
Priority: minor Milestone:
Component: website Version:
Keywords: Cc:

Description

Highlights (&relation, …, &box) included in the current map view on osm.org will not be shown on the embedded map.

Example: http://www.openstreetmap.org/?box=yes&bbox=10.18%2C50.24%2C10.24%2C50.26&relation=23419 Now go to Share menu and select HTML. Look at the produced code.

"Share/HTML" leaves away those features. It would be nice if they either
*were also included in the code and shown on the embedded map OR
*if the user of the "Share/HTML" feature would be informed that those features are missing. For example by changing the currently shown info text "Paste HTML to embed in website" to: Paste HTML to embed in website. Note that only the current map dimensions and the layer selection will be transferred to the produced HTML code

Background: Confused users - see comment "… but the embedded map doesn't have the relation shown at all …" at https://help.openstreetmap.org/questions/420/

Change History (5)

comment:1 Changed 5 years ago by TomH

I'm right in thinking this has always been the case? It's not a regression with the move to the new sharing panel?

comment:2 Changed 5 years ago by aseerel4c26

@TomH: yes, that could be.

comment:3 Changed 5 years ago by TomH

  • Type changed from defect to enhancement

comment:4 follow-up: Changed 5 years ago by TomH

I'm not at all sure we want to allow this to be honest - it's potentially very dangerous from a load perspective if somebody uses it to stick a map somewhere that has a large and complex relation on it.

comment:5 in reply to: ↑ 4 Changed 5 years ago by aseerel4c26

You mean accidental DDoS of osm.org? hmm...

What about changing the text for now? It is only shown if somebody really clicks on "HTML" - so it is not cluttering the sidebar (I guess showing the text only if the current URL contains a not supported feature parameter is too much overhead). Or want we want to just forget that use case for simplicity?

Note: See TracTickets for help on using tickets.