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

Use case (content author): Lazy-load the map viewer #232

Open
Malvoz opened this issue Oct 5, 2020 · 0 comments
Open

Use case (content author): Lazy-load the map viewer #232

Malvoz opened this issue Oct 5, 2020 · 0 comments
Labels
discussion: use case a possible use case: should it be included? what should it say? section: map viewer Capabilities & use cases for declarative map viewer widgets status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft

Comments

@Malvoz
Copy link
Member

Malvoz commented Oct 5, 2020

This issue is for discussion of the use case “Lazy-load the map viewer”, its examples & list of required capabilities.


This use case is about lazy-loading fetches initiated by the map element (or rather any of it's child elements, perhaps only those fetching tilesets) when the map viewer is out of viewport. Not to be confused with lazily loading tiles as described in Capability: Load additional map tiles when they pan into view.

Related web specification:
https://html.spec.whatwg.org/multipage/urls-and-fetching.html#lazy-loading-attribute

@Malvoz Malvoz added discussion: use case a possible use case: should it be included? what should it say? status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft section: map viewer Capabilities & use cases for declarative map viewer widgets labels Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: use case a possible use case: should it be included? what should it say? section: map viewer Capabilities & use cases for declarative map viewer widgets status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft
Projects
None yet
Development

No branches or pull requests

1 participant