Unexpected Cursor Offset when hitting Enter
See original GitHub issueUsing GitHubs’s new video upload feature, here’s the bug. When pressing enter, for some reason the cursor skips a line. The expected behavior would be for the cursor to go to the next line and with a few spaces similar to when it’s Prettified
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:27 (12 by maintainers)
Top Results From Across the Web
Unexpected cursor behavior on ENTER key after mark · Issue #3600 ...
Go to the rich text example Place your cursor after a mark range, e.g. after the italicized word "much" Press ENTER key Cursor...
Read more >InvalidDataAccessResourceUsa...
It's resolved by setting the property to false. Thought to verify if its OK to set it to false in case no cursor...
Read more >The Curious Case of Cursor Jumping - Mutually Human
Cursor jumping is simply when the cursor jumps from one location to another, unexpectedly, while the user is typing into a text field....
Read more >Lagging cursor in Word while using arrow keys
Hello, As of a few days ago, my cursor in Word cannot keep up with my arrow keys. For example, if I press...
Read more >Preserve cursor position when filtering out characters from a ...
In this lesson, we will create a filtering function that accepts new text and current cursor position, and which returns the filtered text...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also experienced this issue. Following @halvespereira 's instructions where I removed
graphiql
entirely, installedgraphiql@1.3.0
(which works), and then upgraded tographiql@1.3.2
which still fixed it.I definitely suspect some sort of dependency issue is at play.
@acao have you done anything to the code? It suddenly works in development and in production. At least it does now.