Repository navigation
fix(ui): draw the op list in the dark theme - #84
Merged
Merged
Conversation
Each op in the list left of the monitor is a <button>, and `.op-list .op` never cleared the browser's button styles. Ops showed as light gray boxes with centered text and a raised border, and the light gray text on them was hard to read. Clear the background, border, font and alignment so the existing dark rules show: the panel color by default, a lighter row on hover, and the blue tint and left bar when selected. Closes #81 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 16, 2026
|
🎉 This PR is included in version 0.5.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #81
Stacked on #83. Merge this into
fix/ui-clip-file-namesfirst, then merge #83 into main, so both fixes ship in one release.The op list on the left of
clip ui, from the same workspace before and after. Row 2 is selected and row 3 is hovered.What
.op-list .opinsrc/ui/web/src/styles.css: background, border, border radius, font, text alignment, width and text color.--bg-1) with--borderdividers. A hovered op turns--bg-2, and the selected op gets--accent-softwith the--accentbar on the left.Why
<button>, and the rule never cleared the browser's default button look. Ops showed as light gray boxes with centered text and a raised border, and the light gray text on them was hard to read.Release
Merging this PR publishes nothing, because it lands on #83's branch. Merging #83 into main then publishes one patch (0.5.2) with both fixes and the README changes already on main since 0.5.1. #81 closes then, from the
Closes #81line in this commit's message.Checks
pnpm lint: pass. The 7 warnings are already on main, all intests/.pnpm type-check: pass.pnpm test: 845 passed, 27 skipped.pnpm build: pass./verify: typecheck, lint and build pass. Tests showUNMAPPED, because no test coversstyles.css. The screenshots cover it instead.vitedev and a scratch API server, with ops from a demo workspace (three imported clips and a trim). Checked the default, hover and selected states, and long paths now end in an ellipsis.codex review --base main): no findings. Its summary: "No actionable regressions were identified." Nothing to fix or rebut.