Cursor artifact under the bottom row #4415

Open
opened 2026-01-30 23:47:16 +00:00 by claunia · 0 comments
Owner

Originally created by @egmontkob on GitHub (Oct 12, 2019).

Originally assigned to: @zadjii-msft on GitHub.

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2762.0

Steps to reproduce

Prefer bar or box cursor shape for more prominent behavior.

Produce more than a screenful of output so that the cursor is in the bottom row.

Resize the window so that there's a noticeable gap (a partial row) under the bottom text row.

Again make sure that the cursor is in the bottom row.

When the cursor is visible (that is, not in "off" state while blinking), scroll back by exactly 1 line e.g. by hitting Ctrl+Shift+Up.

Expected behavior

Option 1: Hide the cursor.

Option 2: Display the partial cursor, and display the corresponding line of the terminal buffer too in this partial row. Also, make sure the cursor keeps blinking as desired.

Actual behavior

The cursor is displayed in the partial bottom row (although no text is printed here – the next prompt in case of this screenshot). Furthermore, it stops blinking.

wt-cursor

Originally created by @egmontkob on GitHub (Oct 12, 2019). Originally assigned to: @zadjii-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): 0.5.2762.0 ``` # Steps to reproduce Prefer bar or box cursor shape for more prominent behavior. Produce more than a screenful of output so that the cursor is in the bottom row. Resize the window so that there's a noticeable gap (a partial row) under the bottom text row. Again make sure that the cursor is in the bottom row. When the cursor is visible (that is, not in "off" state while blinking), scroll back by exactly 1 line e.g. by hitting Ctrl+Shift+Up. # Expected behavior Option 1: Hide the cursor. Option 2: Display the partial cursor, and display the corresponding line of the terminal buffer too in this partial row. Also, make sure the cursor keeps blinking as desired. # Actual behavior The cursor is displayed in the partial bottom row (although no text is printed here – the next prompt in case of this screenshot). Furthermore, it stops blinking. ![wt-cursor](https://user-images.githubusercontent.com/5750745/66703477-5b186e00-ed13-11e9-9b0f-407adfcd6c99.png)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4415