Skip to content

What is legendLinks? #80

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

Closed
zcorpan opened this issue Jun 29, 2020 · 6 comments
Closed

What is legendLinks? #80

zcorpan opened this issue Jun 29, 2020 · 6 comments

Comments

@zcorpan
Copy link

zcorpan commented Jun 29, 2020

    readonly attribute LegendLink[] legendLinks;

What is this?

@prushforth
Copy link
Member

It is used to make available the set of <link rel="legend" href="..."> links that are included in the layer's document, and the first such link is rendered as a <a href="...">layer-name</a> in the layer control entry for the layer:

image

@ahmadayubi
Copy link
Member

It might be worthwhile thinking about having legends rendered on top of the map in one of the corners. As most modern web maps containing legends have them visually represented on the map itself as an image (i.e. Google Map JavaScript API ).

@prushforth
Copy link
Member

I'm more on the side of leaving this in the domain of custom controls as of now, but they are definitely needed for many maps.

That said, legendLinks[] might not be the right API to support, TBD.

@prushforth prushforth transferred this issue from Maps4HTML/HTML-Map-Element Jul 22, 2020
@Malvoz
Copy link
Member

Malvoz commented Jan 29, 2021

I think the concept of "legend links" is problematic because:

  1. It isn't apparent that the link is a destination for legend information (link name derived from the layer name, in the layer control).
  2. It requires the user to navigate away from the current document to recieve the information (which in the example in What is legendLinks? #80 (comment) is an image with the accessible name of "toporama_en (219×551)", which isn't very useful).
  3. Hard/impossible(?) to define a relationship between an object on a map and its corresponding description (if the object and the description lived in the same document you could perhaps define the relationship using aria-details for example, at least in a polyfill/JS library).

Do we have a UCR issue for this use case and/or capability?

@prushforth
Copy link
Member

Do we have a UCR issue for this use case and/or capability?

If we don't, we should do. It was added to support WMS and WMTS legend links capabilities, because originally I held that support for WMS and WMTS were baseline requirements, so I did my best to accommodate their facilities.

That said, maybe the facility could be reimagined with a better and more accessible UI, and possibly a better API even. Often times a legend is a vital bit of meta-information about the map, and could be super useful for low-vision users etc.

This was referenced Sep 8, 2021
@Malvoz
Copy link
Member

Malvoz commented Sep 9, 2021

legendLinks removed in #213.

@Malvoz Malvoz closed this as completed Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants