Aiirobyte: a routing group of many accounts took so much of the page that
editing the groups below it was a long scroll. The stage folded only runs
of three or more API keys (#1319).
Now:
- Three or more accounts of one provider side by side for one model fold
into one row the way keys do: the count, the lit one and what it does,
how many are available and resting. A request to a folded account flies
to the fold.
- A group in the group's heading folds from a click, Enter or Space (it is
a button now, with a chevron). Folded, it says "{n} on" and what its
seats do together; requests under it fly to the heading and a failure
tags it.
- Accounts and keys sums a provider's accounts up in one row too.
- Keys start folded as before. Accounts and group headings start open
under six, folded from six. What the reader opens is kept in
magpie.routingKeysOpen as before, what they fold in the new
magpie.routingFolded, so both directions survive a reload.
- Redraws go through steady(), so a click keeps the page where it is.
- Strings in en, zh, zh-TW, ja, de. Display only: the gateway's order and
choice don't change.
routing-account-order now opens the relay's key fold by :not(.open),
since the account folds there start open.
Run: new internal/gui/tests/routing-group-fold.test.cjs (defaults, click
and Enter in place with the page not moving, kept across reloads both
ways, a live request to a folded group heading with its tag, Accounts and
keys folds, 420px fit) in Chromium and WebKit, en/zh/zh-TW/ja/de, 40/40.
On origin/main's assets it fails (no account fold, heading not foldable).
All routing-* tests, panel-routing, click-scroll, gui-ja, gui-de,
gui-zh-tw and i18n-keys: 255/255 in Chromium and 255/255 in WebKit. Not
tried in the real window with a live gateway.
yetone
55544f09f6