{"id":"6a9c5387cd6f79cedcd7b7a1","title":"2026 09 05 Issue 181","path":"how-to/committee/release-notes/2026-09-05-issue-181","contentMarkdown":"# 05-Sep-2026 — reload for a new version after ticking boxes, and say when a reload is being held back [#181](https://github.com/nbarrett/ngx-ramblers/issues/181)\n\n## [build 878](https://github.com/nbarrett/ngx-ramblers/actions/runs/33980719159) — [commit c800074](https://github.com/nbarrett/ngx-ramblers/commit/c800074a29246c7c418b319dcd59f4b8c5881719)\n\n_____\n\n## What's new\n\nOpen tabs reload themselves when a new version is deployed, but not while you are editing. Ticking a box or choosing from a dropdown used to count as editing, so a tab could sit on the old version indefinitely without saying so. Now only typed text holds the reload back, and when it is held back a notice at the top of the page says a new version is ready, with a Reload now button.\n\n## At a glance\n\n- Tabs reload after ticked boxes or changed dropdowns; typing still holds the reload back\n- A \"new version of the site is ready\" notice appears whenever the reload is held back","contentHtml":"

05-Sep-2026 — reload for a new version after ticking boxes, and say when a reload is being held back #181

\n

build 878 — commit c800074

\n
\n

What's new

\n

Open tabs reload themselves when a new version is deployed, but not while you are editing. Ticking a box or choosing from a dropdown used to count as editing, so a tab could sit on the old version indefinitely without saying so. Now only typed text holds the reload back, and when it is held back a notice at the top of the page says a new version is ready, with a Reload now button.

\n

At a glance

\n\n"}