The cap-4 composite shipped the coach-mark sliced through the middle of its sentence. Measured, same component and viewport: the leaf renders the pill at bottom 864 of 900, the composite at 919 — clipped by 17px, because the composite adds a ~53px header above its nested child's stage and findMapBox() finds no positioned container to re-parent into. The component's header promises that case degrades to "stay put — a degraded anchor, never a crash". A graceful degradation that degrades to invisible is a failure, not a fallback, so the clamp measures the rendered rect and only ever lifts a pill that is actually clipped. Two wrong attempts are recorded in the code because the reasons matter. Setting style.transform would have destroyed the wrapper's translateX(-50%) centring, and the pill's computed transform also carries the bob animation, so a computed reading is never just my offset. Adjusting the bottom offset composes with the attribution clearance instead of fighting it. Clamping only at nextTick also missed: the composite's layout has not settled then, so the clamp now runs from syncAttribClearance, which already re-fires from a ResizeObserver, plus a second observer on the pill's own layout parent. Verified on six surfaces: the composite lifts 30px to bottom 888, every other surface reports lift 0 and is byte-identical in behaviour, and all six keep centreDelta 0. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| i18n | ||
| layouts | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.