GNOME Bugzilla – Bug 353446
[blocked] Orca not correctly reporting key values in gconf-editor
Last modified: 2011-09-14 13:36:23 UTC
[This is an Orca bug that currently depends upon a bug in another GNOME module. It's been opened here so that if the problem is reported again, it can be closed as a duplicate of this bug. Once the other module problem is fixed, we will be easily able to check whether it fixes the original Orca problem]. Steps to reproduce: 1. Start up Orca. Startup gconf-editor 2. Tab to the table of name/value pairs. 3. Move around in the table with the arrow keys. With the recent change to onActiveDescendantChanged() in default.py, the first column of the values table is now getting spoken, but not the whole row (if Insert-F11 is set to "speak row").
Thank you! We'll keep this blocks/depends relationship so Orca users that read the Orca bug reports know that we're aware of this and are tracking it.
Removing target milestone from [blocked] bugs. We have little control over them, so we're better off letting priority and severity be our guide for poking the related components.
gconf-editor is dead. Long live dconf-editor. Or something like that. Removing the 'depends' on bug 342420.