From the 5B: an observer fires only when the COLUMN resizes. A pane whose height arrives later (styles adopted late
in a shadow root) would have left the link pending, and a pending link blocks the settle's write. check:view-address
covers it: a fresh load whose observer never fires again still opens the link (43 poisons).
Measured in a browser on Country Posters and on Regions: a fresh load with ?pane=<second pane> stayed on the first
pane, with the column's scrollTop 0 at 6 s. The column is built in the composite's onMounted, before it has a
layout, so the pane's offsetTop was 0 when the link was shown. And a ResizeObserver's first callback, which comes
after layout, only recorded the height.
Now the link waits until the column has a height and the pane a top, then shows it once. The wait is the observer's
callback, or a bounded rAF without one. A scroll that settles while the link waits does not overwrite it. The
composite's view readout follows from the scroll event it already listens to.
check:view-address F models a column with no layout at build, whose observer first fires after layout. There are 2
new poisons (42 in all), and restoring the old immediate show in the real file fails the gate.
- ownAddress records only pane and place. tab is the owner's own key, so a nested announcement cannot switch it.
- A shell keeps Regions (and UPG100) alive when another tab is open. Switching back dropped ?pane= and ?place=
(the tab change), while the screen still showed them. pane-wrapper and region-dashboards now watch for being
shown again (a ResizeObserver: no height, then height) and claim their pane / place back with a replace. An
address that names one wins, because Back to an entry of this tab is applied while the column has no layout.
- scrollTo(id, null) behaves as scrollTo(id).
check:view-address covers each of these (34 poisons, each caught). The slow pane-wrapper arm runs only for
pane-wrapper poisons, so the self-test takes 16 s.
The address gets its second and third keys:
- ?pane= is the open view of a composite;
- ?place= is Regions' subject.
Both keep the ONE-writer rule:
- On its own leaf the composite owns the address and writes.
- Nested in a shell it announces, and the shell writes.
- On a partner's page nothing is written; a link is still read.
useViewAddress:
- claimView() is the one call for a reader's choice: the owner writes it, any other element announces it.
- ownAddress() lets an owner record its nested elements' announcements, and stops them there.
- An announcement carries only the view keys, one event per action.
- pane and place are siblings: a tab change drops both, but a pane change keeps the place, because Regions keeps
its region while the reader is on the list.
pane-wrapper (buildPaneColumn) takes an opt-in `address`:
- a link opens its pane without writing;
- a click is a push, and a selection made by the same click rides in the same push (one Back step);
- where the reader's scroll settles is a replace;
- Back/Forward scroll and never write;
- the first pane is the default and is never written.
Regions:
- regions-mfe opts its column in and records its panes' announcements on its own leaf. A list click opens the
dashboard with its place in one write.
- region-dashboards claims ?place= instead of writing its #slug with its own pushState (replace at first paint,
push on a choice, re-applied on Back). An old #slug link still opens, and on its own leaf it is rewritten to
?place=.
- urlSync:false now guards only the tab title.
check:view-address adds:
- E: nested claims and the owner;
- F: pane-wrapper on a simulated column;
- G: the Regions wiring.
The census drops region-dashboards (5 writers now). Self-test: 29 poisons, each caught. Real-source mutations are
caught too.
scrollTo(paneId) called target.scrollIntoView(), which scrolls every scrollable
ancestor, the embedding page included. On another site, "Map" / "Show on map"
moved the host's own page so that the map's top met the window's top, and a host
shorter than the window then showed its white space under the map. The column
is the scroller (position:absolute; overflow-y:auto) and each pane's
offsetParent, so col.scrollTo({ top: target.offsetTop }) lands the pane exactly
and leaves the page alone.
Comments in library/ and internal/ that quoted a person, attributed a decision to one, used first person,
named fleet agents or carried private host names now state the same technical fact in neutral words:
poster-render (including the comments it writes into generated posters), packet-render, the poster and
research scripts, PosterWall, DataTable, the legends, the layouts and the gates. The network-policy note
states the policy itself. Behaviour is unchanged: a few printed gate messages and reason labels drop an
agent name, the poster-render integrity pin follows its comment-only edit, and series.json changes only in
its _meta and _why notes. The historical poster design snapshots (library/scripts/posters/snapshots/),
which nothing reads, are removed.
The root of the paint-over and of the keyboard regression rega's A/B found.
ProfileLoader's wrapper is min-height: var(--profile-min-h, 100dvh), and a
host that already sizes the element sets --profile-min-h:0 (the Gallery's
.dms-pane, VerticalTabs, plugin-studio). The pane column sizes each element
(inset:0 in its pane) but never set it, so on the standalone leaf each
pane's wrapper was 100dvh = 900 px inside an 843 px pane: the wall's
scroller ran 57 px past its pane, its first row's tapes painted over the
map, and Tab into those tapes scrolled the pane COLUMN (and, with the
clip, onto an invisible control). The Gallery was pane-sized only because
its own host set the variable. The clip stays as belt and braces.
overflow:hidden alone leaves each pane a scroll container: focus() or
scrollIntoView() on content in the overflowing first card row (a Tab
into the tapes) would scroll the PANE and shift the wall inside it.
overflow:clip clips paint without making a scroll container, and like
hidden makes no containing block for position:fixed, so the modal scrims
still cover the viewport. hidden stays first as the fallback for engines
without clip (dx-shepherd's review).
The UPG-100 wall's first card row runs past the list pane's bottom into
the map area on every surface (rega's census on ca07fc3c8: cards to y 142
against a pane ending at 57; 14 wall elements inside the map area at
1440, 6 at 390, leaf and Gallery, both engines). On the standalone leaf
the tapes' z-index painted that overflow OVER the map pane: the 'PRINT
OPTIONS' fieldsets across the top of the map, the reported defect. The
Gallery hid it only by a stacking difference.
.pane gets overflow:hidden, so content outside a pane is clipped at the
pane, whatever the host's stacking contexts. Not contain or isolation:
either would make each pane the containing block or stacking context for
position:fixed modal scrims and trap them under a host's nav rail, the
regression VerticalTabsLayout records. The map roots are inset:0, so the
map and its attribution are pane-sized and unaffected.
