Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I1016

The Cockpit works on a phone and before JavaScript runs

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
capability-graph
Milestone status
ACTIVE
Wave
4
Waiting on
I1009
Holds back
I1021
Behind it in all
3
Evidence
0 of 3
In the waySubjectDetail
issueI1009I1009 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1016

majordomus plan verify I1016

majordomus plan done I1016

What it is

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.
Now
The Cockpit is server-rendered with its own stylesheet, and its behaviour across viewports has not been established for this material.
Wanted
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.
Done when
unknown: the record declares no `completion`
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.

Acceptance

  • 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-probebash test/run.sh
Evidence required
viewports_passzero_js_baselineaccessible
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
share/cockpit/src/cockpit.css
Not
Hiding content below a breakpoint instead of adapting itRequiring JavaScript to discover a documentation link
Depends on
I1009
Priority
p0
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-06
Updated
2026-09-06
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.