Bug 482401

Summary:	Different behavior of key modifiers in wayland and x11
Product:	[Plasma] kwin	Reporter:	zvova7890
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	fanzhuyifan, nate
Priority:	NOR
Version:	5.27.10
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=482980
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description zvova7890 2024-03-04 17:58:20 UTC

SUMMARY
When you are using an X11 session and, for example, use the left/right arrow keys to move the cursor around the text, you can press the arrow key and periodically press the control modifier to change the cursor jump strategy from character-by-character to word-by-word. The sequence of pressing the keys doesn't matter; you just press control when needed to switch to the word-by-word style.

On Wayland, control needs to be pressed first, and it also doesn't allow modification during arrow key presses. The X11 behavior is more comfortable for me; however, I don't know if that's a bug or a feature.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.8-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
Memory: 28,2 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Micro Computer (HK) Tech Limited
Product Name: Venus series

Comment 1 fanzhuyifan 2024-03-05 00:38:52 UTC

Which apps are you seeing this in?

Comment 2 zvova7890 2024-03-05 01:16:48 UTC

Kate, konsole, kdevelop, remmina, chromium, firefox... probably all applications.

Comment 3 fanzhuyifan 2024-03-05 01:26:04 UTC

Still an issue as of plasma 6.

Comment 4 zvova7890 2024-03-05 01:49:33 UTC

Correct

Comment 5 fanzhuyifan 2024-03-05 02:47:53 UTC

As per discussion in the kwin channel, on wayland the apps are responsible for generating key repeats. So this would need to be reported to the apps, or the underlying toolkits (Qt).

Comment 6 zvova7890 2024-03-05 15:16:41 UTC

Wow... I wonder why no one has implemented this correctly. 

UPD: I've checked it on chromium again - it is working as intended. So, need to report this to Qt and GTK at least. Firefox seems using GTK input subsystem.
XWayland seems also doing fine.