-
Notifications
You must be signed in to change notification settings - Fork 12
Use case (content author): Lazy-load the map viewer #232
Copy link
Copy link
Open
Labels
discussion: use casea possible use case: should it be included? what should it say?a possible use case: should it be included? what should it say?section: map viewerCapabilities & use cases for declarative map viewer widgetsCapabilities & use cases for declarative map viewer widgetsstatus: suggestionthis issue discusses a suggested addition to the report, that is not yet in the draftthis issue discusses a suggested addition to the report, that is not yet in the draft
Description
Metadata
Metadata
Assignees
Labels
discussion: use casea possible use case: should it be included? what should it say?a possible use case: should it be included? what should it say?section: map viewerCapabilities & use cases for declarative map viewer widgetsCapabilities & use cases for declarative map viewer widgetsstatus: suggestionthis issue discusses a suggested addition to the report, that is not yet in the draftthis issue discusses a suggested addition to the report, that is not yet in the draft
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