1.0.18 — offline mode keeps its promise, updates stop interrupting

[nyblnet]

1.0.18 is a security release. Offline mode did not block everything it promised. Please update — and there is an awkward wrinkle in how you update, which the first section explains.

Offline mode now keeps its promise

The switch says "nothing leaves this computer". Five things still went out with it on:

• a manual Check for updates called the release server
• Manage languages… downloaded the pack index, and any pack you added
• a deck's video or image pointing at a web address still loaded from it
• requests already in flight were left to finish
• a second tab already in a live session kept syncing edits

The last two are the ones that matter most. A remote image or video in a document is the cheapest tracking beacon there is — it tells whoever hosts it that you opened the file, and when — and offline mode is exactly what you would turn on before opening a deck you did not write. The second tab was worse: real document content kept moving.

Separately, where a browser refuses site data — a private window, or a locked-down setup — the checkbox showed the switch as on while nothing had been stored, so it did nothing at all. It now holds for the session regardless, and says plainly that it will not survive a reload.

The fix is structural rather than a list of patches: the network is reachable from exactly one place in the code, everything else goes through it, and flipping the switch now cuts connections that are already open rather than only the next one.

The awkward part

One of the paths that leaked is the update check itself. So if you are on 1.0.17 with the switch on, you cannot reach this fix without doing the thing you turned the switch on to prevent.

There is a clean way round it: download a fresh copy from bento.page and open your deck in that, rather than updating in place. Or turn offline mode off for the moment it takes to update, then turn it back on — the leak is a request to the release server, not to anyone else.

Reported privately. Updating is per-deck, because each file carries its own copy of the app: About → Check for updates, or start from a fresh download. Updating writes a new file and leaves the original alone.

Updating a file no longer interrupts you

With Bento Tray installed and a folder granted, Update this file now finishes without a single dialog. The backup it leaves behind is saved beside your document instead of being downloaded — so the copy you would roll back to sits next to the thing it backs up, rather than in your downloads folder.

Two things used to cause that prompt. The backup was handed to the browser's download machinery, which asks where to put things if you have told Chrome to. And an update of a double-clicked file described itself to the extension as an export, so the extension — correctly — refused to write it for you.

Without the extension it is still a download, exactly as before.

Share fits inside the menu now

Narrow the window enough to fold the toolbar into ⋯, open the properties panel, then open Share from that menu: the popover was drawn sliced down its left edge, with the panel showing through the gap where the rest of it should have been.

Share and Language now open as a section of the ⋯ list itself — full width, scrolling with it, nothing hanging over an edge to be cut off. Wide windows were never affected; the fold only happens when the toolbar runs out of room.

The cause is worth knowing if you write CSS: the ⋯ menu scrolls when it holds more than fits on screen, and a box that scrolls in one direction quietly clips the other whether you asked for that or not. Anything floating inside it was always going to be trimmed.

Also

• The update card in About drops an accent stripe that was the only one of its kind in the app, and stayed peach in dark mode while everything around it themed. The accent is still on the button you press.

Full notes: CHANGELOG · release

One thing worth repeating

Opening a .bento.html someone sends you means running that file's own code. That is inherent to a format where the file is the application. Offline mode is a real boundary and it now holds — but treat a deck from a stranger the way you would treat any HTML file from a stranger.

Questions in Q&A, ideas in Ideas, bugs in issues.