altseven 9.1.4

Child-render race fix, falsy-key lookups, and event listener isolation.

The 9.1.x series is a set of correctness fixes to the rendering and data layers. Applications vendoring dist/a7.js should rebuild and update.

9.1.4 — child views are no longer destroyed by a startup race

View.render() treated a missing mount point as fatal — but for a child view, a missing mount point usually just means “my parent hasn’t painted yet”. A child whose setState() is driven by an async fetch could lose that race and be silently, permanently destroyed: dropped from its parent and the UI manager with nothing to re-create it. Whether it happened depended on how fast the fetch resolved — speeding an endpoint up could break a view.

Now the framework distinguishes “not yet” from “gone” using the parent’s hasRendered flag: children of an unpainted parent stay registered and paint when the parent does. Top-level views with missing selectors are still unregistered — that remains a real misconfiguration.

9.1.3 — falsy keys are misses, not “everything”

Model.get( name, key ) and Service.get( ID ) treated any falsy key (null, 0, "") as “no key given” and returned the entire backing Map — an undetectably wrong answer, because a Map is truthy and objecty enough to pass every if (item) guard. The failure surfaced arbitrarily far from the cause. Both now distinguish absent from present: get() with no argument returns everything; get(0) is a lookup that honestly misses and returns undefined. The same fix removed a wilder symptom: an id-less object binding in a DataProvider received the whole cache Map as its bound entity.

Code that relied on get(null) (or get(0), get("")) for the full collection must call get() with no argument.

9.1.2 — one throwing listener no longer kills a topic

publish() invoked listeners directly, so a non-function entry (e.g. { "topic": null } declaring a topic) or any listener that threw aborted every listener after it — silently. Listeners are now isolated: bad slots are skipped, throwing listeners are logged via app.log.error, and dispatch continues.

9.1.0 — managed WebSocket sessions

webSocketSession( options ) adds a managed session layer over raw sockets: exponential backoff with jitter, ping with optional pong-timeout (zombie detection), online/visibilitychange listeners that reconnect immediately, and a beforeReconnect callback distinguishing permanent (return false) from transient (throw) failures. See WebSockets.

See the repository’s release_notes.md for the full details of every change.