(cache)How come keys pressed during a lag are applied in the wrong order after the lag?

exerceo · 10-05-2025, 11:38 AM

Keys pressed during lag are applied in an incorrect order. For example, pressing CTRL+W and then Ctrt+Shift+Tab during a lag should close the current tab and then go to the last tab after the lag, but the opposite happens: it switches to the last tab and closes the last tab.

Is this a known bug? Is this deliberate?

(Regarding the lag: It's not the fault of Linux. It's due to my habit of hoarding too many tabs.)

frankbell · 10-05-2025, 08:05 PM

A quick web search indicates that maybe you should tell us more about the hardware. For example, is this a USB keyboard, a laptop, or what?

scasey · 10-05-2025, 08:43 PM

Also, in which application? A web browser? (which one?) Something else?

pan64 · Yesterday, 02:03 AM

lag means something does not (cannot) work properly, in this case the key event processing. Don't forget, both pressing and releasing a key may generate an event. The event must also be delivered to the focused window, which may be invisible in case of delay like this. (so the keypress will be processed by something which is not [yet] displayed). This behavior also depends on the implementation of the given software.
Returning to the original question, yes, it is known that if you overload the system, this can happen.

exerceo · Yesterday, 11:11 AM

Quote:

Originally Posted by frankbell

A quick web search indicates that maybe you should tell us more about the hardware. For example, is this a USB keyboard, a laptop, or what?

Wireless (non-bluetooth) keyboard connected through a USB receiver.

Quote:

Originally Posted by scasey

Also, in which application? A web browser? (which one?) Something else?

Firefox.