[ENHANCEMENT] Restore editor scroll position after closing diff view

[XiaoYingYo]

Problem (one or two sentences)

When using the diff viewer to review changes, after clicking 'Accept' or 'Reject', the focus returns to the file editor, but the cursor is always moved to the beginning of the file. This forces the user to manually scroll back to the location of the changes, disrupting the workflow.

Context (who is affected and when)

This issue affects all users who rely on the diff viewer for code reviews and accepting AI-generated changes. It occurs every time a diff view is closed, regardless of the file type or the complexity of the changes.

Desired behavior (conceptual, not technical)

After closing the diff viewer (either by accepting or rejecting the changes), the editor for the corresponding file should automatically scroll to the position that was last visible in the diff viewer. This ensures a seamless transition and allows the user to immediately continue their work from where they left off.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

I'm exploring a potential fix for this issue that restores the editor scroll position after closing the diff view. This will help maintain workflow continuity when accepting or rejecting changes. I'll open a PR to share progress.

Opened PR #9283 with my attempt at addressing this issue. The solution captures the visible ranges before closing the diff view and restores them when showing the text document, ensuring the scroll position is maintained. All tests are passing. Feedback welcome!

I see your feedback that the current fix is not working properly - the cursor still moves to the beginning of the file instead of maintaining the last viewed position in the diff viewer or editor. I will investigate this further and update the PR with a proper solution. Thank you for testing and reporting this issue!

Updated PR #9283 with an improved fix for the scroll position restoration issue.

The previous implementation only captured visible ranges (viewport bounds), but not the actual cursor position. The updated fix now:

1. Captures both cursor position and visible ranges - Prioritizes restoring the exact cursor location where the user was working
2. Handles text selections - If text was selected, it preserves and restores the full selection range
3. Smart fallback logic - Falls back to the midpoint of visible ranges if no cursor position is available
4. Optimized scrolling behavior - Uses InCenterIfOutsideViewport to avoid unnecessary scrolling when the position is already visible

This should now properly restore the editor to exactly where you left off when accepting or rejecting changes. All tests are passing. Please test the updated PR and let me know if it resolves the issue!