Red Hat Bugzilla – Bug 717734
Cannot access facts dialog via accessibility api in subscription-manager-gui
Last modified: 2011-12-06 12:21:41 EST
Description of problem:
In subscription-manager-gui, the expandable cells in the 'view systems facts' dialog cannot be accessed via the accessibility api (at-spi).
Version-Release number of selected component (if applicable):
This is not necessarily a bug per say, but a feature request that would provide a work around - and unblock automation of this dialog.
The 'view system facts' dialog presents its information as a tree. By default all items in the tree are hidden except for those items at the upper most layer. You would then have to expand that tree item to view its children. In the accessibility api, you would do this by using the "expandtablecell" function. This function however is broken in this instance due to some yet to be determined reason - be it within gnome, the api, or the command server itself.
I propose the following: Double-clicking on any item in the tree that has children will either show or hide its children depending on it's current state. You could double click anywhere within the table row to do this, and not just the tiny arrow icon. This would make this dialog consistent with the behavior of many other tree views in other programs thus making it easier to use, and it will unblock automation of this window.
Additionally this view does not recognize any keyboard input, and is unnavigable without a mouse. It would be in the interest of general accessibility if keyboard commands could expand/collapse items in the tree (via arrow keys and/or space/enter) and access the 'update facts'/close buttons (with alt+u, alt+c).
Added expand/collapse to the tree view via mouse double clicking or by Space, Shift+Space, Return or Enter.
in commit 0e91e7c5cf1792ee263ed03743735c41fd0f1f6e in master
VERIFIED in the above version. This works with double clicking, space, return and enter as per keyboard navigation conventions.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.