Bug 459269 - Cannot type the first character with accent in the search field of Kickoff due to search field not being focused by default
Summary: Cannot type the first character with accent in the search field of Kickoff du...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) widget (other bugs)
Version First Reported In: 5.27.80
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: usability
: 393440 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-09-17 11:59 UTC by Patrick Silva
Modified: 2024-07-31 23:25 UTC (History)
4 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 Patrick Silva 2022-09-17 11:59:49 UTC
SUMMARY
Can reproduce on both X11 and Wayland sessions of Arch Linux (Plasma 5.26 beta) and neon unstable.


STEPS TO REPRODUCE
1. open Kickoff
2. try to type any of the following accented characters in the search field:
ã
á
â
ü
à
3. 

OBSERVED RESULT
The character typed in the step 2 appears in the search field without the accent.
If I trpe the same character again without closing Kickoff, it appears with accent, as expected.

EXPECTED RESULT
we are able to type the first character with accent

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Graphics Platform: Wayland
Comment 1 Nate Graham 2022-09-22 17:20:36 UTC
I suspect this is because the search field doesn't start with focus. Does the problem go away for you if you explicitly focus it by clicking in it, before typing?
Comment 2 Patrick Silva 2022-09-22 17:23:56 UTC
(In reply to Nate Graham from comment #1)
> Does the problem go away for you if you explicitly focus it by clicking in it,
> before typing?

Yes.
Comment 3 Nate Graham 2022-09-23 18:11:03 UTC
I can reproduce that. So the issue here is that typing those characters only works when a text field is actually focused, because they rely on modifier keys to generate.

There's no problem for ASCII characters which can be forwarded straight to the text field, but this doesn't work with non-ASCII characters that need to be generated by the user.
Comment 4 ironman466 2022-09-27 09:49:12 UTC
This also happens with fcitx on Neon 20.04. First character I type is always english regardless of language setting of user.
Comment 5 Patrick Silva 2024-07-31 23:25:35 UTC
*** Bug 393440 has been marked as a duplicate of this bug. ***