fix(web): mouse back/forward over the right panel no longer moves the main chat#30882

Approvability

Verdict: Approved at 205bfb7

Macroscope's review found this PR approvable — Mouse back/forward presses over the right panel now stay within preview navigation instead of moving the main chat. The change is localized to mouse-event handling and reuses existing history controls.

No code changes detected at 2077719. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

Explain Change →

No actionable comments were generated in the recent review.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

External image Recent review info

External image Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: fix/issue-30854
• File: .coderabbit.config.ts
• Commit: 205bfb7
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Team
• Run ID: 6996f558-8481-41a2-a1e5-9622de7acac1

External image Commits

Reviewing files that changed from the base of the PR and between 6fbba9233fcea227a988ac548d7422ba8442a244 and 205bfb748fa760dd35a0df9342a6c42105bf9786.

External image Files selected for processing: 4

• apps/web/src/components/RightPanelTabs.browser.test.tsx
• apps/web/src/components/RightPanelTabs.tsx
• apps/web/src/components/preview/PreviewView.tsx
• apps/web/src/contextMenuFallback.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

The automated pipeline stopped on this pull request and will not merge it:

someone else pushed to fix/issue-30854 (head is now f3dd6552a1); the pipeline does not build on commits it did not review

It stays open for a person to finish or close.

Evidence

Proven in the real web and Linux desktop apps: panel thumb presses switch to Thread A on base; head keeps Thread B selected. Browser Back/Forward navigates its page history on head. Main-chat Back/Forward works on both commits.

Environment for every capture: Linux, 1440×900, light theme, isolated synthetic replay-thread fixtures. Web uses Chromium; desktop uses Electron under Xvfb. No live user database was used.

Steps: Open A then B and establish both backward and forward thread history around B. Follow Browser fixture links through pages 1 → 2 → 3. Press native Back/Forward over its address bar, tab strip, and page content. Repeat over Diff content, its tab strip, and its fallback context menu. Dismiss the menu and verify main-chat navigation. Separately, repeat over the desktop Browser device-size toolbar after loading the same three pages through its address bar.

Recordings include scripted history resets between independent presses; each tested panel press starts on Thread B. Stills below show the result after Back. Recordings also cover Forward and controls.

Web driver · Desktop driver · Isolated launcher · Launcher helper

Observed outcomes · All capture URLs, including Forward and controls

AI-assisted; verified with the tests and tools listed above.

Not shown:

• Terminal, Files, Device, Side chat, and pull-request surfaces were not exercised; Diff was the non-Browser surface specified in the reproduction.

Evidence

Open A then B, follow Browser links through three pages while retaining control, and press Back/Forward over the address bar and Browser tab. Repeat over expanded Diff content, its tab and open context menu; check main-chat navigation. In Electron, target actual address-addon padding, then enable the hosted device toolbar and press Back/Forward over its padding.

Environment: Chromium web client at 1280×800 and built Linux Electron at 1280×840, light theme, fresh synthetic databases and identical drivers on both commits. Trusted CDP mouse input drove the real apps. The scenario runner exited 0: base failed and head passed.

Recordings: Before web · After web · Before desktop · After desktop.

Full scenario table including Forward captures · Proof manifest.

Scenario source · Browser setup patch · Browser launcher · Desktop driver · Reproduction instructions.

The saved desktop driver was rerun against fresh state on both commits. All twelve regenerated PNGs were byte-identical to the submitted captures and observations matched. SHA-256 rebuild audit · Rebuilt baseline recording · Rebuilt head recording.

Scope: the paired proof retains Browser control. Watching mode remains unproven; an exploratory head run after releasing control still changed threads on Back over the disabled URL input.

AI-assisted; verified with the tests and tools listed above.

Not shown:

• Watching mode is not proven fixed: an exploratory head run after releasing Browser control changed threads on Back over the disabled URL input. The completed paired proof retains control, matching the supplied link-following reproduction.