Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gtk gtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1.6k
    • Issues 1.6k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 240
    • Merge requests 240
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container 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
  • GNOMEGNOME
  • gtkgtk
  • Issues
  • #1739
Closed
Open
Issue created Mar 12, 2019 by Samuel Thibault@sthibaulDeveloper

Rework the accessibility stack for GTK4

Hello,

commit feb8975a removed the key snooper API, which the accessibility layer was depending on to get keyboard events. The net result is that the screen reader can not get the keyboard event, thus not being able to tell them to the user and breaking a lot of scripts.

Would it be ok to not reintroduce the snooper API, but at least reinstall

case GDK_KEY_PRESS:
case GDK_KEY_RELEASE:
  if (_gtk_accessibility_key_snooper (grab_widget, (GdkEventKey *) event))
    break;

to fix back accessibility?

Edited Apr 01, 2020 by Emmanuele Bassi
Assignee
Assign to
Time tracking