Skip to content
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

Capability: Subscribe to map events #69

Open
NickFitz opened this issue Jun 14, 2019 · 1 comment
Open

Capability: Subscribe to map events #69

NickFitz opened this issue Jun 14, 2019 · 1 comment
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete

Comments

@NickFitz
Copy link
Contributor

@NickFitz NickFitz commented Jun 14, 2019

This issue is for discussion of the required API capability “Subscribe to map events”.

@NickFitz NickFitz added discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? status: placeholder there's a matching section heading / some text in the report, but it's far from complete section: client-side API Capabilities & use cases for client-side APIs labels Jun 14, 2019
@AmeliaBR AmeliaBR changed the title Capability: Subscribe to map move events Capability: Subscribe to map events Feb 7, 2020
@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented Feb 7, 2020

This currently covers any events emitted by the map based on user interaction (and maybe other things like loading?)

If we find, when describing existing implementations / use cases / etc, that particular event types need more detailed descriptions, we can separate it out into separate capabilities.

NickFitz added a commit to NickFitz/HTML-Map-Element-UseCases-Requirements that referenced this issue Jun 5, 2020
As mentioned in the issue, it is probably necessary to distinguish and expand upon different kinds of events (such as those from controls) in a separate capability or capabilities, but I think this gives us a starting point.
NickFitz added a commit to NickFitz/HTML-Map-Element-UseCases-Requirements that referenced this issue Jul 1, 2020
As mentioned in the issue, it is probably necessary to distinguish and expand upon different kinds of events (such as those from controls) in a separate capability or capabilities, but I think this gives us a starting point.
NickFitz added a commit to NickFitz/HTML-Map-Element-UseCases-Requirements that referenced this issue Jul 1, 2020
As mentioned in the issue, it is probably necessary to distinguish and expand upon different kinds of events (such as those from controls) in a separate capability or capabilities, but I think this gives us a starting point.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete
Projects
None yet
Development

No branches or pull requests

2 participants