fix(web): make thread archive button always visible on mobile#2423
fix(web): make thread archive button always visible on mobile#2423juliusmarminge merged 5 commits intopingdotgg:mainfrom
Conversation
Mirrors the new-thread-button mobile fix: on touch viewports (max-sm) the archive button cannot be revealed via hover, so make it always visible and pointer-interactive on mobile while preserving the hover/focus reveal on desktop. Also fade out the thread metadata on mobile so the metadata doesn't visually overlap the archive button (matching the desktop hover swap behavior). Both archive button containers are updated — the one used when confirmThreadArchive is enabled and the immediate-archive variant. Co-Authored-By: Claude Sonnet 4.7 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
ApprovabilityVerdict: Approved CSS-only changes making mobile UI elements visible and minor UX improvements (closing sidebar on navigation, better back button handling). No business logic or runtime behavior changes beyond expected mobile responsiveness. You can customize Macroscope's approvability policy. Learn more. |
- Surface the archive action in the mobile sidebar - Keep settings sidebar navigation aligned with the new button
- Delete local .t33 cache and userdata files - Stop tracking session state and signing-key artifacts
Dismissing prior approval to re-evaluate 2fda5ce
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit fa2dd8b. Configure here.
- Hide the mobile drawer when using the back action - Preserve existing browser-history and home navigation behavior

Summary
Test plan
🤖 Generated with Claude Code
Note
Low Risk
Primarily Tailwind class tweaks and sidebar/navigation behavior changes; low risk aside from potential minor layout or navigation regressions on small screens.
Overview
Improves mobile sidebar usability. Thread-row archive controls are now always visible and tappable on small viewports (including both confirm-archive and immediate-archive variants), with extra spacing and metadata fade-out to prevent overlap.
Tightens mobile navigation behavior. The sidebar now auto-closes on mobile when navigating to Settings or switching Settings sections, and Settings back/Escape handling now falls back to routing to
/when there’s no in-app history instead of callinghistory.back()unconditionally.Reviewed by Cursor Bugbot for commit 0eb4d80. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Make thread archive button and sidebar controls always visible on mobile
SidebarThreadRowto allocate more right-side space on small screens via conditionalmin-widthand padding classes, ensuring the archive button is always visible.SidebarChromeFooterand before navigating to a settings section or pressing Back inSettingsSidebarNav.window.history.back()in the settings Escape key handler with an in-app navigation helper that falls back to the home route when no back history exists.Macroscope summarized 0eb4d80.