LivelyKernel / LivelyKernel/lively.next
After clicking to a location in the browser, only arrow keys on the keyboard respond
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
This behavior is very strange (and I'm sure it doesn't happen on Macs, or you would have seen it). When I'm editing in the code browser, and I navigate to a spot with a mouse click, pressing a letter key has no effect. Pressing the space bar causes the browser to scroll (page forward is my guess). Backspace has no effect. Once I press one of right arrow, up arrow, everything works again until I navigate with the mouse.
The only error messages I see in the console are when I press the space bar:
```
[Violation] 'requestAnimationFrame' handler took 73ms
__rootModule___commonjs-entry-35de395a.js:40255 [Violation] 'requestAnimationFrame' handler took 63ms
__rootModule___commonjs-entry-35de395a.js:40255 [Violation] 'requestAnimationFrame' handler took 110ms
```
Two of these messages appear for every space bar press.
Also, -s is being captured by Chrome, so I can't save.
I also tested this in Microsoft Edge (Version 127.0.2651.105 (Official build) (64-bit)) and there is no problem in Edge.
**To Reproduce**
This has to be a system-specific issue. I'm on Windows 11, running Chrome Version 127.0.6533.120 (Official Build) (64-bit). The project is https://github.com/engageLively/galyleo-dashboard
**Screenshots**
**Setup**
- Windows
**Version**: Please paste the lively.next commit on which the problem occurred here (use the copy button of the Version Checker in the bottom left corner).
9c51c586cfca90d3df3c4439a9677adfa40476de
Contributor guide
Research direction
Start in the code browser and reproduce the keyboard behavior on Windows 11 with Chrome 127 using commit 9c51c586cfca90d3df3c4439a9677adfa40476de. Compare the same steps in Edge, checking letter keys, space, backspace, arrow keys, and Ctrl-S. Done means mouse navigation leaves normal keyboard input working and Ctrl-S is no longer captured by Chrome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100