refactor(dashboard): drop FL0W/L0GS/M4TR1X page-links from the tab strip (#1464)
Follow-up to the route swap (#1501): now that every separate page is reachable from the H0M3 hub, the dashboard tab strip should hold only real in-page tabs, not the "→" links out to other pages (mara: "remove links to the pages from dashboard - only actual tabs stay here"). - dashboard.html: remove the `tab-matrix`, `tab-flow`, and `tab-logs` `.tab-link` entries (and the stale `tab-count-flow` pill slot — the operator inbox moved to Y3R C4LL). The dashboard strip is now SW4RM / Y3R C4LL / SYST3M / P3RM1SS10NS / SCH3DUL3S / P33RS / ST4TS / S3TT1NGS. - tabs.js: drop the now-dead `tab-matrix` matrix_gui_enabled gate (the H0M3 Matrix tile is gated by home.js instead) and the obsolete `#tab-count-flow` comment. Kept the contextual deep-links into the log viewer (an agent's logs, a build entry's log) — those are functional content links, not navigation chrome. - flow.css: remove the dead `.dashboard-chrome.flow-chrome` + `.tabbar .tab.active.tab-link` rules — the flow page uses a slim back-link header, not the dashboard tabbar, and `.tab-link` no longer exists anywhere. npm run build green (flow.css 1.8kb). No residual references.
This commit is contained in:
parent
7059ebdebf
commit
91fff60c34
3 changed files with 15 additions and 76 deletions
|
|
@ -4,8 +4,8 @@
|
|||
composer, full-viewport terminal). */
|
||||
|
||||
:root {
|
||||
/* Approximate height of the flow chrome (tabbar + dashboard-chrome
|
||||
padding). The slug banner lives at the page footer on /, omitted
|
||||
/* Approximate height of the flow chrome (the slim back-link header).
|
||||
The slug banner lives at the page footer on the dashboard, omitted
|
||||
on /flow.html since the full-viewport terminal has no normal-flow
|
||||
footer position. */
|
||||
--flow-header-h: 3.6em;
|
||||
|
|
@ -29,35 +29,6 @@ body.flow-shell {
|
|||
var(--bg);
|
||||
}
|
||||
|
||||
/* Flow chrome reuses the dashboard's `.dashboard-chrome` + tabbar
|
||||
so the operator can switch tabs from the flow page without
|
||||
navigating back first. The chrome must be fixed-position (vs
|
||||
sticky on the dashboard) since flow-shell has `overflow: hidden`
|
||||
on body and the main area absolute-positions the terminal. */
|
||||
body.flow-shell .dashboard-chrome.flow-chrome {
|
||||
position: fixed;
|
||||
top: 0;
|
||||
left: 0;
|
||||
right: 0;
|
||||
z-index: 30;
|
||||
margin: 0;
|
||||
padding: 0.4em 0 0;
|
||||
background: var(--flow-frost-bg);
|
||||
-webkit-backdrop-filter: var(--flow-frost-blur);
|
||||
backdrop-filter: var(--flow-frost-blur);
|
||||
border-bottom: 1px solid var(--purple-dim);
|
||||
box-shadow: 0 6px 18px rgba(0, 0, 0, 0.35);
|
||||
}
|
||||
/* Active tab on the flow page is FL0W. Its `.tab-link` styling (the
|
||||
tab strip's right-most entry on the dashboard, where it represents
|
||||
the *link out* to /flow.html) needs to read as the active tab here.
|
||||
`aria-current="page"` flags it semantically. */
|
||||
body.flow-shell .tabbar .tab.active.tab-link {
|
||||
color: var(--purple);
|
||||
background: var(--bg);
|
||||
border-color: var(--purple-dim);
|
||||
box-shadow: 0 -2px 12px -4px rgba(203, 166, 247, 0.4);
|
||||
}
|
||||
.flow-main {
|
||||
position: absolute;
|
||||
top: 0;
|
||||
|
|
|
|||
Loading…
Reference in a new issue