← Back to the screen

Design system portfolio

Design record: Perimeter

The four direction lines behind this page, the generator command that produced its tokens, and the pairs it was measured against.

Cloud security posture across three AWS accounts, built as the page an operator trusts at 3am: side navigation, breadcrumbs, a flashbar, the posture figures, one collection and a panel that answers the row selected.

Direction

LeverDecision
ArchetypeResource console. AppLayout idiom: top navigation, side navigation, breadcrumbs, a notifications bar, a content column that scrolls, and a right-hand panel (split panel at 1280px and wider, a bottom sheet below).
Data stanceEvidence-first. A verdict, one figure, one chart and a measures matrix sit above the table, and every one of them is computed from the 248 rows in the table.
DensityCloudscape compact by default, comfortable on request. space-scaled-* shrinks with the setting; space-static-* does not.
The one bold thingA fix is a change set you read before it runs. Review fix runs preflight checks, shows a before and after, states the cost and the permission, and needs an acknowledgement when real traffic would be cut off. The legend still prints the contrast ratio the browser measures.

Why the archetype changed

The first version was a ten-tile wall display that never scrolled. It answered "is anything wrong" from six metres and nothing else: there was no way to find a finding, read one, filter, sort or act. The owner's brief for this round asks for the console idiom Cloudscape is actually used for, so the wall display went and its best parts stayed: the verdict, the contrast legend, the degraded state, the typed confirmation.

Structure, in the order a visitor meets it

  1. Top navigation. Brand, organization scope, a link back to the portfolio, Display settings, the signed-in user.
  2. Flashbar. On load: three change sets wait for approval, with an action that filters to them. Later: applying, verifying, resolved, suppressed (with Undo), copied, feed stopped. Each updates in place.
  3. Page head. "Security posture", an Info link that opens the help panel, a Refresh button that shows a loading state, and a ticking "Refreshed 14:02:36 UTC, 28 seconds ago".
  4. Verdict, figure, meter, chart. Computed. Twenty-one critical findings against a limit of ten; the meter draws the limit tick and the overage; the chart draws two series by shape and colour, a dashed threshold, end labels, and a cursor with a text readout the arrow keys drive.
  5. Accounts and measures. Stacked bars (each a button that filters the table) and a matrix of seven measures by account. Any count that is not zero links to the findings behind it.
  6. The collection. Property filter with operators and free text, tokens, sortable columns, a select-all checkbox, pagination with ellipsis, and preferences for page size, wrap, compact and striped rows, and which columns show. On a phone the rows become cards.
  7. The panel. One finding in full, a summary of several, or help (status vocabulary, service levels). Resizable by pointer and by arrow keys.

The two states

Reporting. Every feed is live; the trend is solid to today; detectors read 9 of 9.

One feed stopped (Display settings). Security Hub in eu-west-1 goes quiet at 13:41 UTC. The trend stops at the last real reading with no marker; the hero reads 19 verified critical findings and says two more are not verified; sandbox-data's bar, counts and matrix cells become an em dash or are marked; its rows say "Not verified since 13:41 UTC"; detectors read 8 of 9 with an error; and a fix for a sandbox resource is refused at preflight. Zero and no data are different marks.

Figures that check

Everything derives from one seeded set of 248 findings whose quotas are written down: 126, 78 and 44 by account; 21, 47, 108 and 72 by severity. A script confirmed the severity-by-account matrix, the category counts, and the trend against the rows' opened times before the page was built. The numbers that changed from the first version, because they did not reconcile:

Applying a fix removes a row, and the nav count, hero, meter, matrix, chart's today point and verdict all follow, with a brief highlight on each number that moved. Nothing counts up.

Generator

cloudscape_tokens.py --both > tokens.css      # the linked file, never hand-edited
cloudscape_tokens.py --charts                 # the 155 data-visualisation tokens
cloudscape_tokens.py --density                # comfortable vs compact, 24 of 140 differ

tokens.css is generated output. Every colour and every radius on the page is a var() from it.

Status vocabulary, used exactly

StateWhere it appears
successA measure on target; a check passed; resolved
errorA measure over threshold; a service level missed; a check failed; a feed not reporting
warningOff target but not over; a service level due soon; real traffic would be cut
infoA new, unassigned finding; a neutral fact
pendingAwaiting approval
in-progressIn progress; applying; verifying
loadingWaiting on an answer
stoppedDefined in the help panel; nothing on this page has stopped for good

Measured contrast

Every pair sits on color-background-container-content (#ffffff light, #161d26 dark) and every number comes from web-design/scripts/contrast.py.

WhatTokenLightDarkFloor
A value read off a panelcolor-text-body-default18.50:19.98:14.5:1
Critical line, 2pxcolor-charts-red-5005.01:16.21:13:1
High line, 2pxcolor-charts-orange-5005.00:16.23:13:1
Critical bar, filledcolor-charts-red-4004.01:14.99:13:1
Low bar, filledcolor-charts-blue-1-4004.03:14.96:13:1
Primary button labelcolor-text-button-primary-default4.97:18.11:14.5:1

In the light theme the number in a chart token's name is its ratio to the second decimal. In the dark theme it is a floor. The legend prints what the browser measures, so a reader sees the difference rather than taking it on trust.

color-charts-red-300 is 2.998:1 on white and misses the 3:1 floor for a graphic by a thousandth, so the filled bars take the -400 step.

Deviations

Kept warnings

copy-lint.ignore keeps operator-copy, which fires on 0.0.0.0/0. On a cloud security console the CIDR block is the finding itself.

Round two: the count outranks the flashbar

An independent critic, judging the first fold cold, scored this page 6.5: the blue flashbar outweighed the "21" it existed to explain.

Round four

Round nine

Found below the fold, in driven states and at 360px; each fix is one line.

Round ten

A second, colder read. Everything below was found by driving the page at 1440, 1920, 390 and 360 (touch, 3x), both schemes.

Inventions, named

Left

Round eleven (2026-11-10)

Two defects from an independent read at 390 and 360 on a touch phone. Both reproduced before the edit (64 targets under 44px; one approval threw the page from y 3234 to y 39 and left a Resolved notice with only Roll back).

Inventions, named

Found, left

Follow-up: what waits is what this reader can approve

The "Found, left" item above is resolved by deciding the fact one way. The brief gives a change set only for an exposure (the preflight, the before and after, the permission and the cost are all written for revoking 0.0.0.0/0 or turning on Block Public Access, and Review fix is the one bold thing on the four exposed resources). It gives nothing for an inbound rule open to internal addresses on tcp/3389 or an IAM user without MFA: no permission, no before and after, no cost. So those two High rows have no change set awaiting anyone.

Invention: none. The count and the notice now only report what the rows hold.

Round twelve (2026-11-10)

Two severity 2 defects from an independent read, both reproduced at 1440 light before the edit.

Driven at 1440 light, 390 dark, 360 light and 1920 dark, by mouse and by keyboard only, with a double press on Review and on Approve and apply: one dialog, one change set applied, Review inert while applying, focus on the notice at Applying and at Resolved, Roll back one Tab away, no page errors, no horizontal overflow.

Invention: the wording of the hidden reason, a presentation sentence from the change set's own id and state; no product fact.

Driven again at 1440 light, 1920 dark, 390 dark and 360 light by keyboard only, with the whole approval path: open the finding, Tab and Shift+Tab, Enter again, Review, double Approve, Applying, Resolved, Roll back one Tab away. No page errors, no horizontal overflow.

Round twenty-eight (2026-11-10)

One severity 2 and two severity 1 defects from the round 27 read, all reproduced before the edit (1440x900, 1280x720, 1920x1080: after a row 10 open or the Show it path the panel head sat 140 to 645 px above the viewport; 390x844 dialog Apply at top 840 against a dialog ending at 828).

Inventions, named

Left

Round thirty-two (2026-11-10)

One severity 2 and two severity 1 defects from the round 29 read, all reproduced before the edit.

Inventions, named

Left

Round thirty-four (2026-11-10)

Four findings from the round 33 read, all reproduced before the edit (probe at 320, 360, 390, 1440, 1920).

Inventions, named

Left

Round thirty-six (2026-11-10)

Three findings from the round 35 read, all reproduced before the edit (1440x900 for the notices and the keys, Chromium, light).

Inventions, named

Left

Follow-up: the one-fix case at 64px

The reviewer's case is one fix with the panel open: Resolved over the waiting notice. At 140px the stack was barely smaller than 162. Two causes, both cut.

Measured at 1440 and 1920 (panel open, compact), flashbar height, with the table header's top after the header is scrolled into view (bar bottom plus 16):

StateRound 35First passNowHeader top, scrolled in
One fix16214064128 (bar ends 112)
Two fixes26214468132 (bar ends 116)

Identical at 1440 and 1920. With the panel dragged to its widest (640px) the item wraps to a header line over one content line with Roll back inline on the right, and the bar is 86px. At 390 dark and 320 light, with two fixes, the collapsed bar is 184 and 204px (216 and 256 before); the bar scrolls with the page there. Driven again at 1440, 1920, 390 dark and 320 light: expand, collapse, dismiss, focus, no page errors, no horizontal overflow.

Invention: none beyond the earlier ones. The cut text states no new fact; it removes two.

Round thirty-eight (2026-11-10)

Five findings from the round 37 read, each reproduced before the edit (Chromium; 390 dark touch for the stack, 1280, 1366, 1440 and 1920 for the rest) and re-run after the last one.

Inventions, named

Left

Round forty (2026-11-10)

Three findings from the round 39 read. D2 and D3 reproduced before the edit with a keyboard audit that presses every keyboard-reachable action and records document.activeElement (100 presses at 1280: 16 left it on BODY, among them Roll back, Undo on an assign, select-all, Copy from the Actions menu and from the panel, Assign from the panel, Dismiss of the last notice and Refresh, more than the reviewer named). D1 reproduced with a Range probe over the matrix at 49 widths and panel sizes (24 of the 49 clipped words before; at 1280 with the panel at its default, a 669px table in a 520px card).

Inventions, named

Left

Round forty-two (2026-11-10)

Three findings from the round 41 read. All three reproduced before the edit (D1 by the double-press rows, D2 and D3 by the focus audit: Info opened the panel with focus left on the link, and the Undo notice was 51 to 78 Shift+Tab stops away by the reviewer's count).

Every undoable act and where focus goes

ActFocus afterWay backDistance
Review fix, Apply (Resolved)the Resolved noticeRoll backTab 1
Review and approve, Applythe Resolved noticeRoll backTab 1
Suppress (panel, menu, ten)the Suppressed noticeUndoTab 1
Assign to me (panel, menu, ten)the Assigned noticeUndoTab 1
Roll backthe Rolled back notice (round 40)none: it is the way back; Review fix runs it againDismiss, Tab 1
Info link, Enterthe panel headingCloseTab 1
Close, Escthe Info link0

Review fix, Review and approve, Apply and Copy had no double-press hole: Apply twice posts one Resolved and one Roll back, a second Roll back press posts one Rolled back, Copy twice leaves one notice. No change.

Audit

focus-audit.mjs (copied from round 40, extended) records the Tab and Shift+Tab distance from the focus after each act to its Undo or Roll back, a double-press row per act (keyboard, double-click, from the Actions menu, Undo twice, out-of-order Undo) and each Info link's focus after open, Close and Esc. At 1280 and at 390 (touch): 0 rows on BODY, every distance 1 by Tab (the other direction is 48 to 99), no double press makes two notices, every Undo returns the rows to the state before. Page errors: none. Two audit faults were fixed on the way, not page faults: the row snapshot compared the selection count, which Suppress and a fix clear by design, and one scenario pressed the rail button with the panel already open, which closes it.

Inventions, named

Round forty-four (2026-11-10)

Two severity 2 findings and one severity 1 from the round 43 read. D2 and D1 reproduced before the edit; the stacked flashbar, the never-evict rule (data-keep), restOn and the focus audit are all kept.

Audit

focus-audit.mjs (copied from round 42) now records the page's scroll between two flashbar controls in every Undo and Roll back distance row, fails a row whose Tab distance is more than 1 (it failed on the nearer of the two directions before), and waits for a phone's smooth scroll to settle first. New rows: Assign then Copy, Assign, Copy, Copy again, Suppress then Copy, Assign then Copy ARN from the panel, Suppress, Assign, Copy, Resolved then Copy, plus Assign twice from the menu and from the panel (the cue is beside the control, no notice is added, it goes after 4 s). The scroll is read on the Tab pass only: the Shift+Tab pass arrives at the bar from the far end of the page, which a phone scrolls smoothly, so it measured the animation and not a jump. Plus a row for Assign then Refresh. Result: at 1280, 179 presses, 0 bad; at 390 dark touch, 162 presses with 0 on BODY, then every distance row run again with the Tab-only scroll metric, 18 rows, 0 bad (the 390 control rows that a phone does not render are n/a, as in round 40). Every latest Undo and Roll back is at Tab distance 1 (Shift+Tab 48 to 100), page scroll between flashbar controls 0px, no page errors. Before the edit, the same Assign then Copy (1366x768) left the Undo hidden and focus on Actions.

Inventions, named

Left

Round forty-six (2026-11-10)

Two severity 2 findings and one severity 1 from the round 45 read. Both severity 2 reproduced before the edit. Round 44's flashbar fix, the never-evict rule (data-keep), the stack and the cue are kept; the focus rule of rounds 42 and 44 is replaced.

Every undoable act and where focus goes

ActControl pressedFocus afterWay backTab distance
Assign to me (panel, one or ten)staysAssign to meUndo after it, and the notice's1 (back to the control: 0)
Assign to me (Actions menu)stays (Actions)ActionsUndo after it, and the notice's1 (0)
Copy (ARN button, Actions menu)staysthe control pressednone to give(0)
RefreshstaysRefreshnone to give(0)
Page changestaysthe pager buttonnone to give(0)
Suppress (panel, menu, ten)gonethe Suppressed noticeUndo1
Review fix, Review and approve, Applygonethe Resolved noticeRoll back1
Roll backgonethe Rolled back notice (round 40)Review fix runs it againDismiss, 1
Undo (inline)gonethe control that did the actnone0
Undo (notice), Dismissgonethe finding it brought back, else the next notification, else the page headingnone
Info link, Enterstaysthe panel headingClose1
Close, Escthe Info link0

After a later plain act the Undo is where it was: Assign then Copy from the Actions menu leaves focus on Actions with the Undo still one Tab on; Assign then Copy ARN in the panel leaves focus on Copy and the Undo two Shift+Tab back (beside Assign) or in the notification. Suppress then Copy: focus on Actions, the Suppress Undo in its notification only (57 Tab stops), because Suppress left no control to carry one.

Audit

focus-audit.mjs (copied from round 44) now measures, after each act, two things. The Tab distance back to the control pressed: expected 0 (the focus after the act is that control; a row that left it is bad), for Assign (panel, ten in the panel, Actions menu), Copy after Assign (menu, ARN in the panel), Copy twice, Assign then Refresh, Suppress then Copy, Resolved then Copy. The Tab distance to the nearest Undo or Roll back, in a notification or beside the control: expected 1 (0 or 1) after Assign, Suppress and Resolved, and after Copy where the Undo's control is still the one holding focus; also the distance to the notification's own button, which must exist. New rows: the inline line and Undo sit directly after the button; Tab 1 is the Undo; inline Undo returns focus to the control and rows to the state before; notification Undo removes the inline one; Actions Assign, same; Copy and Copy again keep focus; Refresh keeps focus; both Undos together restore once; an older act's Undo leaves the newer inline Undo; Next page speaks the page and keeps focus. Result at 1280 (light): 197 presses, 0 on BODY, 0 bad. At 390 dark touch the first run was 182 presses with 5 bad rows, all one fault the audit found: on a phone the Actions menu Copy still sent focus to its notice (reveal takes focus). Copy from a menu now only scrolls the notice into view there (reveal(node, true), focus stays on Actions); the Copy rows were run again at 390 and 1280: 0 bad. Scroll walk at 1280x800, 1366x768, 390x844 and 320x844 touch: 0 bad rows, the only moves being a wrap from the last control to the top and the rail entry above. Page errors: none.

Inventions, named

Left

Round forty-eight (2026-11-10)

One severity 2 and three severity 1 findings from the round 47 read. All four reproduced before the edit (1280x800, keyboard): root and three Enters gave three "root" chips; prod-pay, ArrowDown, Enter, Enter gave Account = prod-payments and a stray "prod-pay"; Tab from Cancel in Review fix with Apply disabled landed on BODY; Esc on the grip of the help panel closed it (panel width 0); Tab from Next page to the rail moved the page from 2202 to 1576 with the rail 226px above the viewport. Rounds 42 to 46 (focus rests, the flashbar, the scroll-padding-top regions) are kept.

Filter test table (filter-test.mjs, 1280x800, keyboard unless stated)

PathChips after
root, Enter"root"
root, Enter x3"root" (was three)
prod-pay, ArrowDown, Enter, EnterAccount = prod-payments (was plus "prod-pay")
Account = prod-pay, ArrowDown, Enter, EnterAccount = prod-payments
empty box, Enter x2none
ArrowDown, Enter (property), ArrowDown, Enter (operator), ArrowDown, Enter (value)Severity = Critical
root Enter, root Enter"root" once, "That filter is already applied." spoken
prod-pay, ArrowDown, Enter, done twiceAccount = prod-payments once
root Enter, prod-pay ArrowDown Enterboth
root, Esc (list closes, text stays), Enter x2"root" once
root, Esc, Esc (clears the box), Enternone
Backspace on an empty box, then Enterlast chip removed, nothing added
Backspace x2 with two chipsnone
ArrowDown on an empty box, Enterthe box reads "Severity ", no chip
root, ArrowUp, Enter"root"
root Enter, Tab away, Shift+Tab back, Enter"root"
pointer: type root, press the option; click the box, Enter x2; type root, press the option again; remove the chipone chip, one chip, one chip, none

20 rows, 0 bad.

Audit

focus-audit.mjs and scroll-walk.mjs (copied from round 46) re-run after the last edit. Focus audit at 1280: 197 presses, 0 bad; at 390 dark touch: 182 presses, 0 bad; no page errors. Scroll walk at 1280x800, 1366x768, 390x844 and 320x844 touch: 0 bad rows; pager to rail is 0px at both desktop sizes. dialog-test.mjs: 8 Tab and Shift+Tab presses in Review fix with Apply disabled stay on Cancel; with Apply enabled they alternate Cancel and Apply; Suppress with its button disabled and enabled, and Preferences (20 controls), never leave the dialog; PageDown with Apply disabled scrolls nothing (1710 before and after).

Inventions, named

Left

Round fifty (2026-11-10)

Four severity 1 findings from the round 49 read (ship note: the rail). All four reproduced before the edit at 1280x800 and 390x844 touch (repro.mjs). Rounds 42 to 48 (focus rests, the flashbar, the scroll-padding-top regions, the filter and modal rules) are kept.

Rail key test (composites.mjs, 1280x800 and 1440x800, keyboard)

StartKeysFocusPage scroll
DetailsArrowDown, ArrowDown, ArrowUp, ArrowUp, End, Home, End, ArrowDownHelp, Details, Help, Details, Help, Details, Help, Details0px on all 8
Help (pressed with Enter)Enterthe panel opens, aria-pressed true
HelpShift+Tab, Tabthe panel Close button, Help

Roving tabindex is 0 on the focused button and -1 on the other after every key.

Audit

focus-audit.mjs and scroll-walk.mjs (copied from round 48) re-run after the last edit. Focus audit at 1280: 197 presses, 0 bad; at 390 dark touch: 182 presses, 0 bad; no page errors. Scroll walk at 1280x800, 1366x768, 390x844 and 320x844 touch: 0 bad rows. tabtbl.mjs (Tab onto the table region) and phone-apply.mjs (the notice position every 400ms after Apply, five findings) are new. Screenshots at 1440 light, 1280 light, 1920 dark, 390 dark, 360 light and 320 light: no page errors, scrollWidth equals clientWidth in every state.

Inventions, named

Left

Round fifty-two (2026-11-10)

Two severity 2 findings and one severity 1 from the round 51 read (ship note: the typed phrase). Both severity 2 reproduced before the edit. Rounds 42 to 50 (focus rests, the flashbar, the scroll-padding-top regions, the filter, modal and rail rules) are kept.

Phone sort test (phonesort.mjs)

For each of the eight columns, both directions, at 390, 360 and 320, once with selectOption (the touch path) and once by keyboard (focus the select, ArrowDown or ArrowUp to the value): the first page's order equals the order the desktop header gives at 1280 for the same column and direction, the header's aria-sort reads the same, and focus stays on the sort control. Select all by tap and by Space: 10 rows ticked, the header box ticked, "10 selected"; one row unticked gives indeterminate and "9 selected"; select all again ticks all ten, again clears. Paging keeps the sort, and select all follows the page. 446 checks, 0 bad, no page errors.

Inventions, named

Audit

focus-audit.mjs and scroll-walk.mjs (copied from round 50) re-run after the last edit: focus audit at 1280: 197 presses, 0 bad; at 390 dark touch: 182 presses, 0 bad; scroll walk at 1280x800 and 390x844 touch: 0 bad rows; page errors none (the first 1280 run had parts 4 to 6 crash the page on load, under memory pressure, and they were run again clean). Screenshots at 1440 light, 1280 light, 1920 dark, 390 dark, 360 light, 320 light, 667x375 and 568x320: scrollWidth equals clientWidth in every state. New: dlg-rects.mjs, phonesort.mjs, pf-popover.mjs, selfit.mjs (does the widest option fit each select at 320 to 767).

Round fifty-four (2026-11-10)

One severity 2 and two severity 1 findings from the round 53 read (ship note: dismissing a notification from mid-page). The severity 2 and the chart reproduced before the edit; the second Assign did not reproduce as silent. Rounds 40 to 52 (focus rests, the flashbar, the scroll-padding-top regions, the filter, modal and rail rules) are kept.

Dismiss matrix (dismiss.mjs)

Eight notice types (waiting, waiting then Assign so one remains, Assign, Copy, Refresh, Suppress, the feed warning, Resolved) at five scroll positions (top, chart, findings, table middle, pager), by mouse and by keyboard: 80 rows at each of 1280x720, 1440x900 and 390x844 dark touch. A row is bad when focus is on BODY or out of view, or the focused element moves more than 1px in the viewport (except from the top of the page, where the bar leaving moves the page up by itself). 0 bad at all three; the first run before the edit at 1280x720 gave 8 bad of 10 for the waiting notice alone (1615 to 0 by mouse and key).

Inventions, named

Left

Chart labels stay inside the chart box (coordinator's addition)

Found on the way, then asked for: the bold end label "21 critical" ran 6px past the chart box's right edge at 390, 360 and 320 (box 349, text 355 at 390). Two measured fixes in drawChart, no new text:

Audit

focus-audit.mjs, scroll-walk.mjs and dlg-rects.mjs (copied from round 52) re-run after the last edit: focus audit at 1280: 197 presses, 0 bad; at 390 dark touch: 182 presses, 0 bad; scroll walk at 1280x800 and 390x844 touch: 0 bad rows; dlg-rects.mjs over six sizes: 186 positions, 0 bad; page errors none. The chart-label edit came after those runs; it touches only drawChart, so after it I re-ran labels.mjs, states.mjs (320, 390, 1280x720) and check.sh, not the focus audit or the walks. New: dismiss.mjs, chart.mjs, cue.mjs, cue2.mjs, states.mjs, labels.mjs, shot320.mjs. Screenshots at 1440 light, 1280x720 light, 1920 dark, 390 dark, 360 light and 320 light (chart with the cursor on the annotation, the page after a mid-page dismissal): no page errors, scrollWidth equals clientWidth in every state.

Round fifty-six (2026-11-10)

Two severity 2 findings and two severity 1 from the round 55 read (ship reservation: the filter's free text). All four reproduced before the edit (d1.mjs, misc.mjs, filter-table.mjs; 1280x720, 1366x768, 1440x900). Rounds 40 to 54 (focus rests, the flashbar, the scroll-padding-top regions, the filter, modal and rail rules, the dismiss rule, the chart labels) are kept.

Free-text table (filter-table.mjs, 1280 and 1440, every column on, 50 per page, 248 rows read from the rendered cells)

For each word the filter count, typed into the box and entered with nothing highlighted, against the count of rendered rows whose text contains it (both read from the page; neither calls matchTok):

ColumnQueryFilterRows with it
Severitycritical2121
Severityhigh4747
Severitymedium108108
Severitylow8787
Service levelpast by188188
Service leveldue in6060
Service leveldue in 12121
Openedsep6464
Opened8 sep1212
Statusawaiting approval11
Assigneeunassigned7272
Regioneu-west-14444
Findingbucket4848
Accountprod-platform7878
first row, every cell14 wordsequalequal

26 queries, 0 bad. Against the page: the headline reads 21 critical and 47 high, and critical and high give 21 and 47; Past by 188 and Due in 60 make the 248.

Row position table (d1.mjs, row top in px, before to after, the row's own Enter and click; End and a pointer drag to 640px)

ViewportRowOpenEndDrag
1440x9001, 5276, 584 (same)samesame
1440x90010464 to 738 (whole, panel head 48)738738
1366x7681, 5276, 584 (same)samesame
1366x76810398 to 606606606
1280x7201, 5298, 606 (same)samesame
1280x72010385 to 558558558

36 cases: before, 36 of 36 cases moved (64px for rows 1 and 5 on open, up to 1,330px on resize) and 26 left the row not whole on the screen; after, 0 not whole on the screen, 0 page errors, 6 moved (row 10, the limit above). The panel's top is at 48 (under the top bar) in all 36. Also: Info link opening help, 200 to 200; a second row clicked with the panel open, 529 to 529 and 507 to 507; Esc during a drag restores 400 and the row; a wheel during a hold ends it.

Inventions, named

Audit

focus-audit.mjs, scroll-walk.mjs and dlg-rects.mjs (copied from round 54) re-run after the last edit. The first run of the scroll walk, before the panel-head limit above, had one bad row (open the last row, Tab to Close panel: the page scrolled 559px, the panel's head being above the top bar); that is how the limit was found. After it: focus audit at 1280: 197 presses, 0 bad; at 390 dark touch: 182 presses, 0 bad; scroll walk at 1280x800, 1280x720 and 390x844 touch: 0 bad rows; dlg-rects.mjs over six sizes: 186 positions, 0 bad; page errors none. New: d1.mjs (row position), filter-table.mjs, misc.mjs (matrix Tab, grip Escape), extras.mjs, extras2.mjs (a region off screen still scrolls to its head), dockgeo.mjs, shots.mjs. Screenshots at 1440 light, 390 dark, 360 light, 1920 dark, 1280x720 light and 320 light (the free-text filter, the 10th finding opened, the panel dragged to its widest, the help panel): no page errors, scrollWidth equals innerWidth in every state.