After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 700105 - Hardware keycode with broadway
Hardware keycode with broadway
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Broadway
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-05-10 20:23 UTC by Marc-Andre Lureau
Modified: 2018-05-02 15:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marc-Andre Lureau 2013-05-10 20:23:25 UTC 
Just wanted to open a bug to track status and open discussion.

Ok, broadway use keysyms at the moment. The following commit explains it:

commit 01da867dac948205f10c4ccfd924a2958ad3c749
Author: Alexander Larsson <alexl@redhat.com>
Date:   Thu Apr 14 21:13:28 2011 +0200

    [broadway] Emulate hardware keycodes in keyboard events
    
    We can't really know the client side keymaps, so we use the keysym
    as the hardware keycode (essentially claiming to have a keyboard with
    one key for all possible keysyms). This is not ideal, but its hard to
    do better with no knowledge of the client side keyboard mappings.
    (And html keyboard events suck badly...)


However, this limits severely remote desktop clients usage of broadway, which will have to handle GDK keysyms -> XT keycode translations themself, and this is a bad idea, as it's ignorant of keyboard layout too etc..

Perhaps Broadway could still send the browser keycode (even if they are not hw keycode atm).  The spice-html5 backend has a reasonably nice working browser keycode -> AT/XT mapping ...
Comment 1 Matthias Clasen 2018-02-10 05:14:41 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Marc-Andre Lureau 2018-02-10 10:51:46 UTC 
(still relevant)
Comment 3 GNOME Infrastructure Team 2018-05-02 15:38:02 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/424.