History

Doxa Maps 5ff4da6460 The three Regions roots resolve against their own host box, not the page Each of these shadow roots is position:absolute; inset:0, while its :host had display:block with no position. An absolutely positioned element resolves against its nearest POSITIONED ancestor, and an unpositioned host is not one -- so the root fell through to whatever the partner page happened to have, or to the viewport. It only looked right standalone, where the page fills the viewport anyway, and inside a composite's .pane, which is itself positioned. A partner embedding the element directly gets it painted outside its box. All three are the shadow root's own root element, with only comments between <template> and them, so none of them has a positioned ancestor to fall back on: regions-list.vue:408 .rl-root at :409 region-dashboards.vue:733 .rd-root at :734 regions-mfe.vue:194 .rmfe at :199 dx-shepherd's census named the first as confirmed and the other two as candidates to check. Checked: both are roots, not children of something already positioned, so all three are real. The fix is the house pattern -- position:relative on :host -- matching the already-fixed cities-internet/connectivity-map byte for byte in shape, and prayer-walk-planner.vue:628. One line changed per file. Verified in the ARTIFACT rather than the source: the rebuilt regions-dashboard.js carries all three corrected host rules (two at min-height 320px, one at 420px). check:sfc-parse, check:synced-css and check:one-scroll-container pass; the manifest diff is integrity hashes only, 0 other lines.	2026-09-29 14:38:56 +00:00
..
dx-maps	The three Regions roots resolve against their own host box, not the page	2026-09-29 14:38:56 +00:00
README.md	Gate the country-name join, and record that the wiring was already done	2026-09-29 01:38:07 +00:00

Doxa Maps 5ff4da6460 The three Regions roots resolve against their own host box, not the page

Each of these shadow roots is position:absolute; inset:0, while its :host had
display:block with no position. An absolutely positioned element resolves against
its nearest POSITIONED ancestor, and an unpositioned host is not one -- so the
root fell through to whatever the partner page happened to have, or to the
viewport. It only looked right standalone, where the page fills the viewport
anyway, and inside a composite's .pane, which is itself positioned. A partner
embedding the element directly gets it painted outside its box.

All three are the shadow root's own root element, with only comments between
<template> and them, so none of them has a positioned ancestor to fall back on:
  regions-list.vue:408      .rl-root  at :409
  region-dashboards.vue:733 .rd-root  at :734
  regions-mfe.vue:194       .rmfe     at :199

dx-shepherd's census named the first as confirmed and the other two as
candidates to check. Checked: both are roots, not children of something already
positioned, so all three are real.

The fix is the house pattern -- position:relative on :host -- matching the
already-fixed cities-internet/connectivity-map byte for byte in shape, and
prayer-walk-planner.vue:628.

One line changed per file. Verified in the ARTIFACT rather than the source: the
rebuilt regions-dashboard.js carries all three corrected host rules (two at
min-height 320px, one at 420px). check:sfc-parse, check:synced-css and
check:one-scroll-container pass; the manifest diff is integrity hashes only,
0 other lines.

2026-09-29 14:38:56 +00:00

dx-maps

The three Regions roots resolve against their own host box, not the page

2026-09-29 14:38:56 +00:00

README.md

Gate the country-name join, and record that the wiring was already done

2026-09-29 01:38:07 +00:00

README.md

public/ — the built output

This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:

dx-maps/ — the output folder: 25 plugin bundles and 37 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.
- dx-maps/index.html — the front page: the Plugin Studio, every plugin in one place.
- dx-maps/<plugin>/<plugin>.js — a plugin's bundle (a custom element; load it with a <script> tag).
- dx-maps/<plugin>/<page>/index.html — a ready-made page for one plugin view (embed it in an <iframe>).
- dx-maps/manifest.json — every plugin, page and embed snippet, machine-readable.
- dx-maps/assets/ — the data, fonts and images the plugins fetch at runtime.

The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.