Skip to content

I1016 — The Cockpit works on a phone and before JavaScript runs

Make the Cockpit genuinely usable at narrow viewports and keep its core information present in the served HTML, with JavaScript adding filtering, the graph, live state and search rather than being required to read anything.

BLOCKED wave 4 · p0 · implementation profile · parallel safe

Part of capability-graph — One capability graph, two projections, and no second inventory of what this repository can do.

Blocked. This issue cannot start until I1009 is done. The status is derived from that, not declared.

Objective

Make the Cockpit genuinely usable at narrow viewports and keep its core information present in the served HTML, with JavaScript adding filtering, the graph, live state and search rather than being required to read anything.

Why

A control plane that only works on a wide screen is unavailable exactly when somebody needs it. And information that only exists after a script runs is invisible to anything that does not run scripts, including the tests that check the links.

Current state

The Cockpit is server-rendered with its own stylesheet, and its behaviour across viewports has not been established for this material.

Desired state

Navigation, cards, tables, details and the graph's textual equivalent are usable from a narrow phone width upward, nothing overflows horizontally, and the core content is in the HTML.

Scope

  • share/cockpit/src/cockpit.css

Out of scope

  • Hiding content below a breakpoint instead of adapting it
  • Requiring JavaScript to discover a documentation link

Dependencies

What waits on this

Acceptance criteria

  • Navigation, content, tables and details are usable at narrow phone widths through to a wide desktop, with no horizontal page overflow at any of them
  • Touch targets are usable and focus is visible
  • The markup is semantic, keyboard navigation works, and status is never conveyed by colour alone
  • Core information is present in the served HTML before enhancement

Validation

  • scripts/cockpit-probe
  • bash test/run.sh

Evidence required

  • viewports_pass
  • zero_js_baseline
  • accessible

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

Mobile behaviour is the requirement most often declared done from a resized desktop window. It is asserted at real viewport widths by a browser check.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1016.yaml. Read it back with majordomus plan show I1016.