-
Notifications
You must be signed in to change notification settings - Fork 12
Capability: JS independence #32
Copy link
Copy link
Open
Labels
discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?a specific capability or feature: should it be included? what details? should it be a requirement?section: map viewerCapabilities & use cases for declarative map viewer widgetsCapabilities & use cases for declarative map viewer widgetsstatus: editor's draftthere's a draft section in the report that corresponds to this discussionthere's a draft section in the report that corresponds to this discussion
Metadata
Metadata
Assignees
Labels
discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?a specific capability or feature: should it be included? what details? should it be a requirement?section: map viewerCapabilities & use cases for declarative map viewer widgetsCapabilities & use cases for declarative map viewer widgetsstatus: editor's draftthere's a draft section in the report that corresponds to this discussionthere's a draft section in the report that corresponds to this discussion
This issue is for discussion of the map viewer capability (potential requirement) “Display a basic map without JavaScript”.
From the 2015 use cases report's list of limitations of current tools:
Turning this around, a capability of a web map viewer is its ability to provide at least basic function when JS is disabled or fails for other reasons.