search

LivelyKernel / lively.next

lively.next is a personal programming kit. It emphasizes liveness, directness, and interactivity.
https://lively-next.org
MIT License
65 stars 16 forks source link

After clicking to a location in the browser, only arrow keys on the keyboard respond #1673

Open rickmcgeer opened 2 weeks ago

rickmcgeer commented 2 weeks ago

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

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

linusha commented 2 weeks ago

Does this happen reliably for you? As in, the issue persists even after reloading lively/closing and reopening the browser?

I ask this as we know this bug, I sometimes am a victim to it myself (Chrome on Linux), but we were never able to pinpoint it down or reliably reproduce it.

rickmcgeer commented 2 weeks ago

@linusha closing and reopening the browser seems to take care of it. And it doesm't always happen when I first open the browser. Hmm. An initiation mode that is sometimes triggered and sometimes not?