You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Why a dedicated <feature> element and not <figure> #58
<feature> and <featurecaption> are defined very similarly to <figure> and <figcaption>, and I don't understand why feature captions couldn't contain elements. And accessibility considerations are nearly identical.
Your later comments suggest you answered this, but for the record.
<featurecaption> is intended to be the accessible name of the feature, explicitly marked up. <properties> maps to GeoJSON member properties, except it can contain any HTML markup and <geometry> is a mapping of GeoJSON geometry to markup, so that it can be rendered natively and styled via CSS.
Activity
prushforth commentedon May 9, 2025
Your later comments suggest you answered this, but for the record.
<featurecaption> is intended to be the accessible name of the feature, explicitly marked up. <properties> maps to GeoJSON member
properties, except it can contain any HTML markup and <geometry> is a mapping of GeoJSON geometry to markup, so that it can be rendered natively and styled via CSS.cc @shepazu