vercel / vercel/hyper

Cursor isn't displayed properly at the bottom of the window in new tab

Open
#3,448 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

  • I am on the latest Hyper.app version
  • I have searched the issues of this repo and believe that this is not a duplicate
  • OS version and name: Windows 10 17763.292
  • Hyper.app version: 2.1.1 (Stable)
  • Link of a Gist with the contents of your .hyper.js: Here
  • Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
  • The issue is reproducible in vanilla Hyper.app: Yes

Issue

cursor

If I open new tab, the cursor isn't fully displayed when it's on the boundary of the window. I can solve this by switching to original tab and going back to the new one, but I think it needs to be fixed officially.
Above screenshot is bash mode but the issue occurs regardless of it.

honeycam 2019-01-31 12-25-11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the cursor clipping by opening a new tab in Hyper on Windows 10 and placing the cursor at the bottom window boundary; compare it with switching to the original tab and back. Trace the new-tab terminal window rendering path, and consider the issue done when the cursor is fully displayed without switching tabs, including in bash mode.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.