bento/slides v1.0.10

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.

• Table defaults can follow the deck theme. A deck may now define table
  colours, typography, spacing, borders, and corner radius in theme.table.
  Tables inserted from the toolbar inherit those defaults, and switching back
  from the Minimal preset restores the themed header treatment. Existing decks
  without table defaults keep the same built-in appearance.

• Fix: deleting a slide could empty the deck entirely. The "a deck needs at
  least one slide" guard counted the slides you had rather than the ones that
  would be left — and deleting a slide also deletes its interactive states. So
  a deck holding one slide plus one state of it passed the check, lost both,
  and left the editor with nothing to show. Deletion then appeared stuck. The
  guard now checks what survives.

• Fix: setting a morph id by hand did nothing. Pairing two elements across
  slides via the Morph panel silently failed — the element matched up but never
  animated, so morphing only worked through the duplicate-a-slide route. Both
  ways work now.

• Photos and video now work in live collaboration. This finishes what
  1.0.9 could only warn you about: previously anything past about half a
  megabyte was simply too big to send to your collaborators. Now a large image
  is uploaded once, encrypted, and everyone else pulls it down in the
  background — so you can drop a full-resolution photo into a shared deck the
  same way you would in a deck you're editing alone. A 3MB photo used to
  produce a message the relay refused outright; it now travels as a reference
  of about a hundred bytes.

  As always the server never sees the picture: it is encrypted before it
  leaves your machine, and the relay stores bytes it cannot read. Collaborators
  on the same computer don't involve the relay at all. Small images are still
  carried inside the document exactly as before, so nothing changes for
  ordinary decks, and a self-hosted relay without blob storage keeps working —
  it just falls back to the old inline-only behaviour.