https://bugs.kde.org/show_bug.cgi?id=480490
--- Comment #6 from John <ilikef...@waterisgone.com> --- And more bad news... I have tested how it's the situation in Gnome (version 43.9, Wayland on Debian 12 live mode) And Cinnamon (version 5.8.4, on LMDE 6 live mode) With just the \ shortcut for Kodi and CTRL + + / - and / ' shortcuts for Firefox for Italian and Romanian keyboard layouts. And unfortunately it's exactly the same as in Plasma, they fail the same way and work only the English layout. Because of this comment: https://bugs.kde.org/show_bug.cgi?id=462274#c2 I thought that there is a small chance for this to be Wayland-only, at least on Plasma, but it's not, the problem is there too for al the tested programs and layouts. I'm starting to be inclined to think this is a Linux problem, not a DE or program problem, which others might confirm, having similar problems: https://github.com/celluloid-player/celluloid/issues/576 Sublime text users having this kind of problem too: https://github.com/sublimehq/sublime_text/issues/392#issuecomment-79022157 https://github.com/sublimehq/sublime_text/issues/392#issuecomment-131031043 BTW, in my comment #3, which I cannot edit, this line: \=â - Κodi windowed / full-screen toggle works Should be \=â - Κodi windowed / full-screen toggle fails! Like for Italian where \=ù and Ukrainian where \=ґ And I have finally found a place where \ doesn't work for the English layout too: That is of course when it waits from some text input like if you go: cogwheel (settings) icon -> Add-ons -> Search Now even if you press the \ key, it will actually be inserted into that text field instead of toggling the window size as it normal does for English layout. I got the idea to test this when I saw that someone was saying in a bug report here that there's a difference if the program has a text input field focused or not: https://bugs.kde.org/show_bug.cgi?id=462274#c0 So at least for Kodi, from what I can understand until now, there are 3 cases possible: 1. An active input field present: It will skip any shortcut processing and insert that, be it characters \ (English + Greek), ù (Italian), â (Romanian), ґ (Ukrainian) 2. No active input field present: It will try to process that as a shortcut, which WORKS if \ (English + Greek) 3. No active input field present: It will try to process that as a shortcut, which DOESN'T work and if ù (Italian), â (Romanian), ґ (Ukrainian) are given as they are not recognized as any possible shortcut So I'm wondering, can any code in Kwin detect if a program has an active or focused text input field so it knows to send whatever character in whatever language or if it doesn't, then send only the ones in English (as int that case only shortcuts can be sent ans most of them must be in english)? Can Kwin send characters on 2 different channels, one for whatever texts and one for shortcuts only or only one channel but with some metadata attached so the program knows what is the purpose of those characters (text input or shortcut)?, Can these two comments be of any help of solving this problem?: https://bugs.kde.org/show_bug.cgi?id=434228#c2 https://bugs.kde.org/show_bug.cgi?id=434228#c3 -- You are receiving this mail because: You are watching all bug changes.
