Repository navigation
Stop following the answer while the user scrolls - #4
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe chat now tracks whether it should follow the latest content. Content updates scroll only while following is enabled. Scroll-wheel, live-scroll, and keyboard input pause following. After 0.2 seconds, following resumes when the conversation is within 8 points of the bottom. New submissions and conversation presentation enable following. ChangesChat Scroll Following
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to No confirmed issue prevents merging. Interactive scrolling during streaming should still receive normal validation. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
|
@coderabbitai review |
|
Every streamed token called
scrollTo("bottom"), so scrolling up to reread something mid-answer was yanked back on the next token. Now any scroll the user makes (wheel, trackpad with momentum, scroller drag, the keyboard scroll keys) pauses following, and it resumes only if they settle back at the bottom, send a new question, or open a conversation.Pinning is judged on user scrolls only, never on the stream's own
scrollTo: that one can land a hair short of a document that is still growing, and judging it would unpin the stream by itself.