Repository navigation
desktop: make sidebar filter transparent with circular hover - #2850
Conversation
…ilter-hover # Conflicts: # apps/desktop/Sources/StimDesktop/Views/ViewOptionsMenu.swift
|
Fresh independent review of No actionable findings. Two non-blocking notes and one geometry note below. Verified:
Notes (non-blocking):
Not verified (no build run in this review): that the outer |
Description
The filter control beside the sidebar logo has a persistent native background and a rectangular frame. It should be transparent at rest and have a circular light-grey background on hover.
Solution
Use a plain button with a 28-point square frame, a circle filled with 15% grey while hovered, and the existing icon tint. Preserve the active-filter indicator, accessibility label, tooltip, and popover.
Fixes #2846.
Test plan
Passed desktop
swift build -Xswiftc -warnings-as-errors, Swift format, ASCII and diff checks.Passed root format, lint, build, typecheck and runtime-floor checks.
Built and launched the merged branch (on current
main) withstim macosfromapps/desktop. Resting state is transparent; the options popover opens from the button. The hover capture comes from a local build withisHoveringforced totrue, since the cursor cannot be moved without taking over the screen; the committed code is unchanged.Root tests: 7,726 passed, 87 failed, 20 skipped across 275 files; failures are in CLI process/native-workflow tests. No CLI source changed.
Desktop tests: the full suite had one NodeLauncherTests.recoversTheSameLauncherAfterTheInitialNodeProbeFails failure with Unavailable(); it passed when rerun alone after the parallel load finished.
Knip passed when the generated Swift
.buildfolder was temporarily moved out of the source scan and then restored. The initial scan reported markdownlint from the generated sentry-cocoa dependency.Reran the 14 failing CLI test files with two workers: 13 files passed; packages/server/tests/server.test.ts still had 18 failures (1,674 tests passed). No server source changed.
Fresh independent review of the issue, diff, tests and guidance found no actionable code findings.
No behavioral tests were added for this appearance-only change.