Skip to content

keyboard scancodes inconcsistencies between X11 and Wayland #293

@elinorbgr

Description

@elinorbgr

Wayland forwards the raw keycodes (meaning ESC is 1, 1 is 2, 2 is 3, etc...), while X11 forwards them with a constant +8 offset. This is apparently something known about keymap handling:

See the xkbcommon documentation:

Note that in all current keymaps there's a constant offset of 8 (for historical reasons).

What should we do to be consistent?

  • Should the wayland backend add the +8 offset?
  • Should the X11 backend remove it?

Is there a way we can compare to the other backends?

Metadata

Metadata

Assignees

No one assigned

    Labels

    DS - x11Affects the X11 backend, or generally free Unix platformsS - enhancementWouldn't this be the coolest?

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions