Editors don't keep track scrolling position after switching tabs
Open
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
- Create two tabs
- On the first tab, add random text (say,
1) for 100 lines. - Position the caret on the first line
- Scroll to the last line.
- Switch to the second tab and then switch back to the first tab.
Expected result:
The scrolling position is preserved. That is, I should still be viewing the area containing last line.
Actual result:
The scrolling position is at the first line (where the caret is).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in DrRacket using the listed two-tab steps, then trace the tab-switching and editor-view behavior that restores the caret at the top. Done means returning to the first tab preserves its previous scroll position and the reproduction steps no longer reset the view.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100