A page's own reduced-motion reset never crosses a shadow boundary, so library components rendered inside custom elements slid, faded and spun for readers who asked for less motion: thirteen of them, including the legends and map controls (regions-plugin found it on ProgressBar and named the class). useShadowStyles now injects one prefers-reduced-motion reset into each shadow root it styles, which covers every component styled through it, including later ones. PosterDialog, FilterDropdown and SearchFilterHeader style themselves with <style> blocks and carry their own guard. check:shadow-reduced-motion (in gates:pre): useShadowStyles must inject the reset, and every animating library component must be covered. It fails without the reset (negative-tested) and found the three <style>-block components on its first run. |
||
|---|---|---|
| .. | ||
| charts | ||
| dashboards | ||
| hints | ||
| legends | ||
| map-controls | ||
| poster | ||
| qa | ||
| regions | ||
| search | ||
| tables | ||
| PeopleGroupDetail.vue | ||
| README.md | ||
| ResearchMapFilterPanel.vue | ||
| ResearchMapSideMenu.vue | ||
| SideMenuDrawer.vue | ||
| ViewSelect.vue | ||
| WARNING.md | ||
library/components/ — shared Vue components
The map UI, built from parameterized pieces every app-profile reuses. Fix one here and every map benefits — never edit a shared component to customize one map.
library/components/
┌───────────────────────────────────────────┐
│ legends/ map-controls/ poster/ │
│ charts/ tables/ │
│ PeopleGroupDetail.vue SideMenuDrawer.vue │
│ ResearchMapFilterPanel.vue …SideMenu.vue │
└───────────────────────────────────────────┘
reused by every app-profile via @map/components/…
legends/,map-controls/,poster/each have their own README.- Every component uses
<script setup>, callsuseShadowStyles(), and reaches stores viainject('mapStore' | 'uiStore' | 'dataStore')— never a direct store import.
Full catalog + conventions:
../../documentation/architecture/components.md ·
per-file roles: ../../documentation/reference.md.