Bug 440569

Summary:	Virtual keyboard appears whenever an input field is activated for any reason even when a physical keyboard is attached
Product:	[Plasma] kwin	Reporter:	Nate Graham <nate>
Component:	virtual-keyboard	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aleixpol, arnaud.vergnet, mcpain, postix, rdieter, tgordon681
Priority:	NOR	Keywords:	wayland
Version:	git master
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=441848
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nate Graham 2021-08-03 21:06:05 UTC

Fedora 34 with maliit-keyboard in a built-from-source Plasma Wayland session.

Right now whenever an input field gets focus for any reason, the virtual keyboard appears. This happens for all apps--KDE, GNOME, Electron, and so on. This behavior is annoying and inappropriate for cases when there is actually a physical keyboard attached.

If there is a physical keyboard attached, the virtual keyboard should only appear if an input field is explicitly tapped with a touchscreen. Only when no physical keyboard is attached does it make sense to activate the virtual keyboard for all input field activations.

Comment 1 Aleix Pol 2021-08-04 00:29:40 UTC

Agreed.
I've looked into it and have not entirely found the right hook so everything works properly. At the moment we are abusing the internal keyboard focus property also for touch and I'm afraid changing it will break mayhem (i.e. we don't want to end up with different focus surfaces for the keyboard and touch).

I'm confident it can be done, I've to spend some more time with it to find the right place to change it.

(Of course, if someone beats me to it, it's very welcome).

Comment 2 Nate Graham 2021-08-04 01:48:43 UTC

I'll be happy to test any mayhem-producing attempts :)

Comment 3 Nate Graham 2021-08-04 22:30:35 UTC

*** Bug 440195 has been marked as a duplicate of this bug. ***

Comment 4 Nate Graham 2021-09-01 14:01:48 UTC

*** Bug 441848 has been marked as a duplicate of this bug. ***

Comment 5 Nate Graham 2021-10-24 14:25:27 UTC

Fixed now.