Repository navigation
cmux-next: tune thread minimap contrast - #21183
teamleaderleo wants to merge 2 commits into
Conversation
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Found 5 test failures on Blacksmith runners: Failures
|
|
Unclear: CI failed on
Matched log linesNot re-run automatically: Written by |
|
Agents: |
Summary
Tune the thread minimap's resting and current tick contrast to match the Codex reference measured by PR #20560. The first pass was approximately 25/255 too bright, so quiet ticks now use 0.28 opacity and current viewport ticks use 0.48; hover, focus, and bookmarks still reach full contrast.
This is a focused follow-up to #20560 and is based on
feat/thread-minimap-codex.Validation
git diff --check@base-ui/utilsdependency; no source test failure was observed.Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Tunes the thread minimap resting and current tick contrast to match the measured Codex reference. Quiet ticks now use 0.28 opacity and current viewport ticks 0.48, correcting the first pass which was about 25/255 too bright while hover, focus, and bookmark states still reach full contrast.
feat/thread-minimap-codex.Written for commit 74a6641. Summary will update on new commits.