Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gtk
gtk
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,152
    • Issues 1,152
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 145
    • Merge Requests 145
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • gtkgtk
  • Issues
  • #3597

Closed
Open
Opened Jan 18, 2021 by Emmanuele Bassi@ebassi👣Maintainer0 of 2 tasks completed0/2 tasks

Allow out-of-tree "page" objects to be accessible

Currently we only have in-tree "page" objects, but external libraries (like libadwaita) may want to make their own out of tree objects accessible just as well.

The main blockers are:

  • GtkAccessibleInterface is private
  • the GtkATContext implementation handles page objects specially

This means we're going to need to make the accessibility backend code slightly less "special", to allow out of tree objects to be handled as in tree ones.

Assignee
Assign to
4.2
Milestone
4.2
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gtk#3597