OpenRemote 0.4.6

A private tab stays private, and a new tab shows what you have been reading.

A small release, an hour after 0.4.5, for three things that were worth not
leaving in a published build.

Fixed

• A private tab was being written into this window's history. The console
  promised, in its own design contract, that a private page is kept from history
  and from anything that reads it, and the promise was not kept: the shell said
  which tabs were private and the console never read the flag. It does now, so
  neither the history list nor the address bar's suggestions can name a page read
  in private.
• A peer's browser note had no ceiling. Settings and bookmarks arrive from
  your other devices, and nothing bounded them: one note could carry a million
  rows or a row of a hundred megabytes. There are ceilings now, a note over one
  is refused whole before a single row is written, and the refusal is logged on
  the device that received it.

Added

• The new tab page shows your reading. A new tab used to be a search box on
  an empty page; it now draws the addresses this window has read under it, newest
  first, one row per address, six at most, each opening in the tab. It is the
  same record the history list draws, so nothing in it was read in a private tab.

Smaller

• The address bar's suggestion list, the bookmarks bar and the history list are
  now driven end to end by the project's own DOM smoke: 31 checks, no skips, read
  from a real window rather than from source text.

Known

• An installed app still does not look for a newer version. Moving to a newer
  release means running a newer installer over it, or openremote --update if
  you installed through npm.
• Bookmarks do not follow you to another computer yet, and neither do the pages
  you read. The daemon can already carry browser settings and bookmarks between
  your devices, but the console keeps its bookmarks in its own storage and does
  not write them there yet, so nothing about them leaves this machine.