https://bugs.kde.org/show_bug.cgi?id=462274
Oded Arbel <o...@geek.co.il> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |o...@geek.co.il
--- Comment #3 from Oded Arbel <o...@geek.co.il> ---
I believe I can reproduce the issue on Plasma 6 RC1, my repro is using a
different keys (because my non-English layout has the same shift symbols for
the number row) but I believe it is the same issue.
Reproduction using "/" key on Hebrew layout - in the SI-1452 the "/" key is on
the left-most key of the top character row ("Q" in QWERTY layout):
1. Using the Shortcuts KCM assign some global shortcut to CTRL+/ (in my case I
used the "launch Dolphin" shortcut).
2. Activate a window with a text input and put text cursor in the text input
(for example, in Firefox on bugs.kde.org).
3. Switch to the Hebrew layout.
4. Press CTRL+/
Expected behavior:
Dolphin should be launched.
Actual behavior:
Nothing happens (or some Firefox action might happen if it is bound to CTRL+.)
On the other hand, pressing CTRL+Q (while in SI-1452 layout) does launch
Dolphin.
This is a **very** common issue and - depending on how you look at it - may not
actually be a bug. This factors into the discussion in bug #355046: when
creating a global shortcut with one layout, when another layout is active -
should the global shortcut bind to the physical key on the keyboard or to the
character emitted by the key in a specific layout.
Bug #453661 (which Yevhen added a link from to here), is another instance of
the same issue - though there its more about how to trigger global shortcuts
bound to a character that isn't actually available in the active layout.
But yes - I think these are all the same issue: IMO global shortcut (in
contrast with app-specific shortcuts) should be bound to the physical key,
though there are serious technical hurdles to implement this using the current
Qt-based approach to global shortcuts.
--
You are receiving this mail because:
You are watching all bug changes.
