search

Maps4HTML / HTML-Map-Element-UseCases-Requirements

Use cases and requirements for Maps on the Web
https://maps4html.org/HTML-Map-Element-UseCases-Requirements/
Other
22 stars 12 forks source link

Use case: Custom HTML annotations #37

Open AmeliaBR opened 5 years ago

AmeliaBR commented 5 years ago

This issue is for discussion of the map viewer use case “Display custom web content describing map features”, its examples & list of required capabilities.

This section is currently a placeholder. It may be worth splitting it in two: one for pop-up/tooltip annotations, and one for annotations (legends, data figures, ???) displayed directly in the map layer. Or we can consider this one use case, but multiple capabilities/technological approaches to fulfill it.

There is some overlap with #2, although I'm still not quite certain about how to frame that idea.

Malvoz commented 3 years ago

for pop-up/tooltip annotations

Supposedly these could be built from the emerging/proposed <popup> element.

Malvoz commented 3 years ago

tooltip annotations

There is currently a separate issue for tooltips here: https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/issues/103.

zcorpan commented 2 years ago

Is it desirable for popups in maps to have "light dismiss" behavior? Also see discussion in https://github.com/openui/open-ui/issues/410

prushforth commented 2 years ago

Also see discussion in openui/open-ui#410

If I understand the direction of that discussion, the idea of <popup> may be headed towards a CSS +/- JS proposal, and "light dismiss" is a phrase that describes the ability of the user to close the popup, that would be embodied in a CSS property (values).

Is it desirable for popups in maps to have "light dismiss" behavior?

I believe so, if I go by their described behaviours.