Bug 488346 - Add ability to force touchscreen virtual keyboard to show/hide
Summary: Add ability to force touchscreen virtual keyboard to show/hide
Status: RESOLVED DUPLICATE of bug 466948
Alias: None
Product: kwin
Classification: Plasma
Component: virtual-keyboard (show other bugs)
Version: 6.0.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-11 09:40 UTC by m1vri31c
Modified: 2024-07-06 20:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m1vri31c 2024-06-11 09:40:53 UTC
SUMMARY
Add ability to force the virtual keyboard to show regardless of whether Plasma believes text is being entered. 
Many apps do not have touchscreen support and do not automatically enable the virtual keyboard when tapping on a touchscreen to enter text. Other apps have bugs that don't show it at the right time. Although these should be fixed, a universal fix would be to add the ability to override the automatic show/hide of the virtual keyboard. It would be great to be able to do this with a touch gesture, such as swiping up from the bottom of the screen.

I have also had issues where the keyboard would show up initially but would then disappear when tapping to move the cursor to desired location in the text. Forcing it to display would need to also force it to remain on-screen until dismissed.

STEPS TO REPRODUCE
1. Open LibreOffice with no keyboard connected
2. Tap touchscreen to enter text

OBSERVED RESULT
No virtual keyboard appears

EXPECTED RESULT
Virtual keyboard appears automatically, or user is able to show it manually.


SOFTWARE/OS VERSIONS
NixOS 24.11 (unstable channel)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0 
Qt Version: 6.7.1
Comment 1 Nate Graham 2024-06-11 14:05:48 UTC

*** This bug has been marked as a duplicate of bug 467302 ***
Comment 2 Nate Graham 2024-06-11 14:06:11 UTC

*** This bug has been marked as a duplicate of bug 466948 ***