Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S squeekboard
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 109
    • Issues 109
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Librem5
  • squeekboard
  • Issues
  • #153
Closed
Open
Issue created Nov 14, 2019 by Dorota Czaplejewicz@dorota.czaplejewiczMaintainer

Treating button names as xkb codes is confusing

Keys are currently given either as a string, or as a name of the keycode. There's no way to distinguish those two, leading to confusion: #152 (closed)

The least bug-prone solution is to treat buttons without a "keycode" property as always a string of character.

As a bonus, current behaviour would also be a problem for using text composition interfaces.

Assignee
Assign to
Time tracking