bento/slides v1.0.15

Download the single file below and open it in any modern browser — it's the document, the viewer and the editor in one. Shipped files self-update through the signed release channel.

• Fix: removing a formatting option no longer disconnects the people you are
  working with. While a live session was running, taking something away —
  switching a gradient fill back to solid, turning an outline off, ungrouping,
  unlinking a chart from its table, clearing a click target — crashed everyone
  else's copy of the deck. The person doing it saw nothing wrong; their
  collaborators' sessions stopped applying changes.

  Removing a property is sent as an instruction with no value attached, and one
  line of diagnostic code assumed a value was always there. Adding things was
  always safe, which is why this survived: the convergence tests only ever
  added, so an op that takes a property away had never once occurred in 45,000
  checks. They generate removals now.

• "Save a copy…" and share exports remember their own folder. The save
  picker used one identity for every kind of save, so it opened wherever you
  last put a view-only copy even when you were saving your working file.
  In-place saves, copies and share exports now each remember their own last
  location.

  Underneath, this makes the intent of a save visible to anything hosting
  Bento — tray/ios, and browser hosts — which previously could not tell ⌘S
  from "Save a copy…" at all, because both arrived with identical arguments.

• Fix: the topbar came back in the wrong order after the window narrowed and
  widened again. Below 700px the bar folds its buttons into two menus, and
  unfolding put them back by a rule rather than by memory — everything except
  Redo went into the right-hand group, immediately before Format. So Comment
  migrated out of the insert tools it belongs to, and Save ended up sitting
  after Help. Each button now returns to the group it was authored into, in the
  order the bar was built with.

• Fix: a deck opens where the browser refuses it storage. With site data
  blocked, inside some embedded webviews, or in any sandboxed frame, a Bento
  file showed "This file could not start" and nothing else — because reading
  the localStorage property (not calling a method on it, merely reading it)
  throws in those contexts, and the very first thing the app did was read your
  saved language. One unreadable preference cost you the whole document.

  Preferences now fall back to their defaults instead: the deck opens and
  behaves as it would for a first-time visitor. Anything you change during the
  session works normally; it just is not remembered.