mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-08-03 21:34:40 +00:00
49497f5076
* feat(web-shell): color-code each split pane by workspace On a narrow split (split-screen / mobile), it was hard to tell which workspace each pane belonged to: a pane's header showed only its session name, and the sole workspace signal — the composer chip at the bottom — collapsed to a bare folder icon that looked identical for every workspace, so the workspace was discoverable only by hovering each one. Surface the workspace where you actually scan — the pane header — and give each workspace a stable accent color so panes read apart at a glance and same-workspace panes read as a group: - Add a colored workspace tag (dot + basename) at the start of each pane header on a multi-workspace daemon, and colorize the header divider with the same accent. The dot never shrinks, so panes stay distinguishable even when the name and session title ellipsize. - Derive a stable per-workspace color from the workspace's position in the daemon's advertised workspaces[], reusing the sidebar session-group palette so the two surfaces speak the same color language. Extracted into a shared workspaceAccent.module.css. - Tint the composer workspace chip with the same accent (folder + faint background) so it stays distinguishable even in its icon-only compact state, instead of a generic folder. Single-workspace daemons are unchanged: no tag, and the header divider falls back to the neutral border. * refactor(web-shell): address review on split-pane workspace accent - Rename workspaceAccent.module.css -> WorkspaceAccent.module.css to match the PascalCase convention used by every other component .module.css; update both import sites. - Hoist the four raw-hex accent colors (red/orange/yellow/green) into shared --accent-* theme tokens in App.module.css, and point the workspace accent module, the sidebar group dots, and the overview badges at them. The palette now has a single source of truth and can't drift between the four surfaces (values are unchanged, so rendering is identical). - Add a compile-time exhaustiveness guard so adding a DaemonSessionGroupPresetColor without extending WORKSPACE_ACCENT_COLORS (and its CSS class) fails the build instead of silently dropping that accent. - Give the pane-header workspace tag role="img" so its "Workspace: <name>" aria-label is reliably announced; aria-label on a bare span (generic role) is not. * refactor(web-shell): address follow-up review on workspace accent - Hoist the four --accent-* tokens out of both theme blocks into the theme-independent .app scope, so they are declared once (the values do not vary by theme) — a genuine single declaration rather than two kept in sync. - Add a dev-only runtime check that every accent color has a matching class in WorkspaceAccent.module.css, closing the gap the compile-time guard cannot cover: CSS modules are typed Record<string, string>, so a renamed/removed class would otherwise silently drop that color's accent. - Rename the "same workspace same color" test to describe what it actually asserts (a stable color per cwd, and distinct colors across workspaces). * refactor(web-shell): address second follow-up review on workspace accent - WorkspaceIndicator tests: assert on imported CSS-module class names instead of string literals, so a CSS-module naming change can't silently make the substring checks vacuous; add an expanded-mode (non-compact) accent test so a refactor that gated the accent on `compact` would be caught. - workspaceColor.ts: run the CSS-class contract check unconditionally — throw in dev, but console.error in production — so a missing class in a prod build is at least diagnosable instead of a silent accent drop. - WorkspaceAccent.module.css: correct the docstring to state exactly which tokens come from where — red/orange/yellow/green from --accent-* in App.module.css, blue/purple deliberately reusing the --agent-* brand tokens. --------- Co-authored-by: wenshao <wenshao@example.com>
140 lines
3.5 KiB
CSS
140 lines
3.5 KiB
CSS
.pane {
|
|
display: flex;
|
|
flex-direction: column;
|
|
min-width: 0;
|
|
min-height: 0;
|
|
height: 100%;
|
|
background: var(--background);
|
|
border: 1px solid var(--border);
|
|
border-radius: 10px;
|
|
overflow: hidden;
|
|
}
|
|
|
|
.header {
|
|
display: flex;
|
|
align-items: center;
|
|
gap: 8px;
|
|
padding: 8px 10px;
|
|
/* On a multi-workspace pane, `--ws-accent` is set by a shared accent class
|
|
(workspaceAccent.module.css) and colorizes this divider into a per-workspace
|
|
strip; it falls back to the neutral border everywhere else, so single-
|
|
workspace panes are unchanged. */
|
|
border-bottom: 1px solid var(--ws-accent, var(--border));
|
|
background: color-mix(in srgb, var(--foreground) 3%, transparent);
|
|
flex: 0 0 auto;
|
|
}
|
|
|
|
/* The `--ws-accent` variable that colorizes the divider above and the tag below
|
|
is set by a shared accent class from workspaceAccent.module.css (also used by
|
|
the composer chip), applied to `.header` when the pane has a workspace. */
|
|
|
|
/* Which workspace this pane's session lives in — a compact colored chip at the
|
|
start of the header, shown only on a multi-workspace daemon. The dot never
|
|
shrinks, so panes stay distinguishable by color even when the name and the
|
|
session title both ellipsize on a narrow split; the full cwd is in the
|
|
native title tooltip. */
|
|
.workspaceTag {
|
|
display: inline-flex;
|
|
align-items: center;
|
|
gap: 5px;
|
|
flex: 0 1 auto;
|
|
min-width: 0;
|
|
max-width: 50%;
|
|
padding: 2px 8px 2px 6px;
|
|
border-radius: 999px;
|
|
background: color-mix(in srgb, var(--ws-accent) 14%, transparent);
|
|
color: color-mix(in srgb, var(--ws-accent) 70%, var(--foreground));
|
|
font-size: 11px;
|
|
font-weight: 600;
|
|
line-height: 1.4;
|
|
}
|
|
|
|
.workspaceTagDot {
|
|
width: 7px;
|
|
height: 7px;
|
|
flex: 0 0 7px;
|
|
border-radius: 999px;
|
|
background: var(--ws-accent);
|
|
}
|
|
|
|
.workspaceTagText {
|
|
min-width: 0;
|
|
overflow: hidden;
|
|
text-overflow: ellipsis;
|
|
white-space: nowrap;
|
|
}
|
|
|
|
/* Per-pane connection-loss indicator: each pane has its own daemon connection,
|
|
so a drop on one shouldn't silently leave stale messages with no signal. */
|
|
.connectionError {
|
|
flex: 0 0 auto;
|
|
padding: 6px 10px;
|
|
background: var(--warning-bg);
|
|
border-bottom: 1px solid var(--warning-border);
|
|
color: var(--warning-color);
|
|
font-size: 12px;
|
|
}
|
|
.connectionErrorText {
|
|
display: block;
|
|
overflow: hidden;
|
|
text-overflow: ellipsis;
|
|
white-space: nowrap;
|
|
}
|
|
|
|
.title {
|
|
flex: 1 1 auto;
|
|
min-width: 0;
|
|
overflow: hidden;
|
|
text-overflow: ellipsis;
|
|
white-space: nowrap;
|
|
font-size: 13px;
|
|
font-weight: 600;
|
|
color: var(--foreground);
|
|
}
|
|
|
|
.closeButton,
|
|
.maximizeButton {
|
|
flex: 0 0 auto;
|
|
display: inline-flex;
|
|
align-items: center;
|
|
justify-content: center;
|
|
width: 26px;
|
|
height: 26px;
|
|
border: none;
|
|
border-radius: 6px;
|
|
background: transparent;
|
|
color: var(--muted-foreground);
|
|
cursor: pointer;
|
|
}
|
|
|
|
.closeButton:hover,
|
|
.maximizeButton:hover {
|
|
color: var(--foreground);
|
|
background: color-mix(in srgb, var(--foreground) 8%, transparent);
|
|
}
|
|
|
|
/* The maximized pane keeps its toggle visually "active" so it's clear which
|
|
control returns to the tiled layout. */
|
|
.maximizeButton[aria-pressed='true'] {
|
|
color: var(--foreground);
|
|
background: color-mix(in srgb, var(--foreground) 10%, transparent);
|
|
}
|
|
|
|
/* The transcript takes the remaining height and scrolls independently per pane. */
|
|
.body {
|
|
flex: 1 1 auto;
|
|
min-height: 0;
|
|
overflow-y: auto;
|
|
display: flex;
|
|
flex-direction: column;
|
|
}
|
|
|
|
.footer {
|
|
flex: 0 0 auto;
|
|
padding: 8px;
|
|
position: relative;
|
|
}
|
|
|
|
.approval {
|
|
margin-bottom: 8px;
|
|
}
|