Settings: give the backup block room to read - #44
Merged
Conversation
Three layout fixes to the backup setting, which had grown until the interval control — the thing the block is actually about — was the hardest part of it to find. - The interval segments now sit level with the description instead of centring against a column that runs a description, a kv table and a thirty-chip tag field tall. Same rail position, no longer floating halfway down the block. - A failed run reports its timestamp and streak on one line; the Job's message and reason move into the existing (i) tooltip. They were a paragraph wrapping inside a right-aligned kv value, which pushed the rest of the table around and made a table worth scanning into prose. - The skip list, its help text and "Back up now" move out of the label column to full width. Thirty chips wrapping in half the measure read as a wall, and the field they belong to is a text input, which wants the whole line. No behaviour change: same controls, same handlers, same requests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #34 / #38 — layout only, no behaviour change. The backup setting had
grown a description, a kv table and a thirty-chip tag field inside its label
column, which left the interval control (the thing the block is about) floating
halfway down the page.
The interval sits level with the description. New
.setting-row.row-topmodifier:
align-items: flex-startfor rows whose left column runs tall. Same232px rail, just found where the block starts.
A failure is one line, with the detail in the tooltip.
Last failurewas atimestamp plus the Job's message plus its reason, wrapping inside a right-aligned
kv value and shoving the rest of the table around. Now the row is
8/5/2026, 10:16 PM (3 in a row)and the message/reason hang off the same(i)tooltip the CLI rows already use — hover or keyboard focus.
.kv b.kv-failturnsoff the ellipsis clipping, which would otherwise eat the tooltip card.
The skip list is full width. Its help text, the tag field and
Back up nowmove out of the label column and below the cost warning, so the chips wrap across
the whole measure instead of stacking six rows deep in half of it.
bk.error("Could not launch") is left as it is — one short string, and it stillfits its row.
Verified by rendering
SettingsViewagainst stubbed backup status in both thehealthy and failing states (a throwaway harness, not committed), at 1100px and at
420px.
npm run build(tsc + vite) clean.🤖 Generated with Claude Code