Release 2.14.0
8 Oct 2026 · pinned package [email protected]
- A boost page move no longer keeps the old navbar. 2.13.3 removed the render's document listeners, but panels.js still held every panel ever registered (the drawer on each render; signed in, the account menu too) in its list, with a MutationObserver, so each re-render kept the whole removed bar and its listeners alive.
OpenVibePanels.register()now takessignal(an AbortSignal: the registration ends when it aborts, its observer is disconnected) and returns itsunregister();OpenVibePanels.unregister(el)does the same by element. The navbar registers its panels with the render's signal, gives the display rows'ov:displaywindow listeners that signal too, and drops a gone render's queued registrations. - browser-harness: the navigation probe forgets a window or document listener when its AbortSignal aborts, as the browser does. It kept every one, and with it whatever the listener closed over, so the growth check also measured its own probe: with 2.13.3's navbar alone it still saw the old bars.
- Measured with ovhost browser-check's method (probe on, forced GC, lap 2 → 5), the patched files served into the live pages: openvibe.codes +780 nodes, +60 listeners → 0, 0; openvibe.services +852, +60 → 0, 0; openvibe.space +744, +72 → 0, 0; openvibe.community +3324, +72 → 0, 0. Both halves are needed: either one alone still grows.
- New test boost-navbar-chrome.test.js (real Chrome: navbar, panels and boost over six laps, measured like browser-check; no node or listener growth, no detached bar); panels.test.js and navbar-brand.test.js cover the signal lifecycle.
- The navbar's notes on
history,silentLogin,fedcmandfedcmLoginmoved to the README (navbar.js 28.8 KB brotli, budget 29 KB).
PagesThe bar’s brandThe menuThe navbarSoft pages
Rules39 The account lives in the menu's You tab, not in a dropdown.31 One navbar per page, owned by the shared Frame.