Ex prompt scrolls page when editor is taller than visible page
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reproducing the ex prompt behavior in a CodeMirror editor whose height exceeds the visible page or container, comparing prompt entry and exit with a shorter editor. Investigate the ex prompt entry point and cursor focus or scrolling behavior; done means the prompt stays within the visible editor area or exiting it restores the cursor view.
Written by the indexing model from the issue text.
Description
When the CM editor is taller than the visible page/container height, opening the ex prompt puts the prompt at the bottom of the editor, and the page/container is scrolled to show the ex prompt. When the user exits the ex prompt, the page/container stays at the bottom of the editor unless a movement re-focuses the cursor.
This is in contrast to a CM editor that's shorter than the visible page/container height, which does not scroll the editor to show the ex prompt.
Is there a way to make the ex prompt appear at the bottom of the visible portion of the editor instead?
Alternatively, can the cursor be re-focused after exiting the ex prompt to scroll the page/container back up to the cursor?
This is sort of a niche use case, but unfortunately it's difficult for us to control the height of the CM editor to make sure the bottom of the CM editor is within the visible page. Ref: https://github.com/jupyterlab-contrib/jupyterlab-vim/issues/144#issuecomment-2328362350. Thanks for your consideration!
- Dominant language
- JavaScript
- Stars
- 470
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
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.
More from replit/codemirror-vim
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
replit/codemirror-vim#276 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
replit/codemirror-vim#264 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
replit/codemirror-vim#251 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
replit/codemirror-vim#243 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
replit/codemirror-vim#239 ·
All issues in replit/codemirror-vim
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·