5008a6ff5f
Some checks are pending
build-gate / build (push) Waiting to run
Both maps drew their legend as a full-width strip (left:8px right:8px -- measured 1264px of a 1280px map, 98.75%), which ran underneath the floating control rail. MapToolbar sits at inset-inline-end:3px with 32px buttons, so any box reaching right:8px intersects it at every viewport; the rail's higher z-index kept the buttons clickable, which is why the defect survived three reports as "looks broken but works". Gospel ran under four of five buttons, cities under two, the difference being only legend height. The legend is now a bounded, left-anchored panel imitating the shared SemanticTreeLegend: left:8px with width var(--map-legend-width,380px). Being bounded on the left, it cannot reach the right rail at all -- a geometric guarantee rather than a tuned z-index. Below 480px it keeps a 46px gap so the rail still clears. Measured after: legend 380px of 1280 (29.7%), zero intersection with all five buttons, 857px clearance, and a dispatched click on the top control landing on button.mcb via composedPath. Mobile at 390px: 336px wide, 11px clearance, zero intersections. Both files kept byte-identical. Both maps also showed the shared "Tap a coloured dot" hint while shading country polygons and drawing no dots at all -- a hint pointing at something the reader cannot see. PinHint documents a pinHint:false opt-out, but the standalone leaf page built its config from a hardcoded object, so no profile could reach that key. <profile>.meta.json now carries an optional `config` map merged into the leaf's BASE_CONFIG, with generator-owned keys reserved and the carrier stripped before the manifest is written so its published shape is unchanged. Both maps opt out; the hint is gone from both. |
||
|---|---|---|
| .. | ||
| src | ||
| dashboard.config.js | ||
| index.html | ||
| index.js | ||
| research-dashboard.meta.json | ||
| research-dashboard.vue | ||