You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The changelog is readable before you take the update — the update card in the sidebar named a version and asked for a 220 MB download and a restart, without saying what was in it. It could not: help/whats-new.json is stamped at build time and bundled, so the note describing v1.80 exists only inside the v1.80 binary, and the copy running on the machine has never held a note for the version it is offering. The one source a running app does have is the GitHub release bodies, which electron-updater already fetches on the availability check and threw away. fullChangelog is on, so a user several versions behind gets every release between theirs and the latest, newest first, rendered as markdown under a What's changed disclosure on the card. A release published with an empty body normalises to null rather than to an empty array, and the disclosure is then absent rather than opening onto blank space.
Changed
Both sidebar announcements are a headline until asked — the what's-new card printed its whole entry, which runs to several paragraphs, at a user who had not asked for it; it is a single title now with the note behind the same disclosure the update card grew. The height cap and the scroll that PRDCT's sidebar-overflow fix introduced move with the note into its expanded state, which is the point at which they matter: these cards live in the sidebar's flex-shrink-0 announcements block, so an unbounded one pushes the session list and the foot panel off the bottom of the window with nothing to scroll.
Fixed
A rendered HTML page keeps its place when you switch tabs — click away from a rendered .html tab and back and the page reloaded from scratch: the scroll was at the top again and anything the page held — an open in-page tab, a filter, a chart's zoom — was back to its initial value. Only the selected file tabs were rendered, so deselecting one unmounted its frame and the whole document with it; a group's or a session's web view had the same gap. The frame is an opaque origin, so its state cannot be read out and restored; what works is never destroying it. Every open file tab now stays mounted and the unselected ones are hidden, exactly as the terminals have always been, and a web view once opened stays mounted behind whatever takes the pane — with its server probe paused while nobody is looking. A hidden pane is aria-hidden and takes no clicks.
Deleting a group stops its quick-launch terminals, and an ownerless one never comes back as a tab — deleting a group killed its member tabs and forgot its terminals: the npm run dev behind the row kept running in tmux with its record on disk, and the next launch, finding no group to hang it off, adopted it as an ordinary tab. Seven mystery rows from two groups deleted the day before. Delete and Ungroup now both stop the group's terminals (members too on Delete), asking first when one is running and saying what it stops; the keybinding ungroup takes the same path and its dialog renders from the app shell, so it shows with the sidebar closed or Settings open instead of ghosting back later. At boot a hidden record whose owner is gone is discarded rather than surfaced, and every tmux kill by name uses the exact-match form, so an absent name can no longer kill its -2 sibling.