Red Hat Bugzilla – Bug 815563
System preferences dialog needs new at-spi locators
Last modified: 2012-06-20 08:56:49 EDT
Description of problem:
It looks like the glade file for the System Preferences dialog in subscription-manager-gui has been copied directly from the register dialog and modified for special use. Normally that's cool, but it seems that none of the at-spi locators were changed, so everything still says "register_dialog" instead of "system-preferences", so it is very confusing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open the system preferences dialog and then look at the locators through your favorite at-spi broswer (like sniff from the dogtail package).
in the file:
you have the following lines for
The window title:
The vbox containing the elements:
<atkproperty name="AtkObject::accessible-name" translatable="yes">register_dialog_main_vbox</atkproperty>
The action area:
<atkproperty name="AtkObject::accessible-name" translatable="yes">registration_dialog_action_area
The close button:
<atkproperty name="AtkObject::accessible-name" translatable="yes">register_button</atkproperty>
All of the <accessibility> </accessibility> sections could be removed; window titles and button objects are automatically given an at-spi locator of the same name. Additionally the vbox and action-area only serve as organizational divisions and are not usable or clickable - therefore don't really NEED a locator either though they could be simply renamed.
Author: Alex Wood <firstname.lastname@example.org>
Date: Tue Apr 24 10:26:36 2012 -0400
815563: Remove incorrect at-spi locators.
Committed 51da3ce32a059800a66bbb83935df593337998d0 to RHEL6.3
Created attachment 580499 [details]
Fixed in the above version.
All things are named properly and all traces of register_dialog have been removed from this window.
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.