After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 163696 - Theme Preferences table lines not spoken immediately
Theme Preferences table lines not spoken immediately
Status: RESOLVED DUPLICATE of bug 163791
Product: gnopernicus
Classification: Deprecated
Component: speech
unspecified
Other Linux
: Normal normal
: ---
Assigned To: mp
mp
AP2
Depends on:
Blocks:
 
 
Reported: 2005-01-11 16:41 UTC by John Crawley
Modified: 2005-01-13 10:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Crawley 2005-01-11 16:41:00 UTC
Using gnopernicus 0.9.17

 - With gnopernicus activated and speech enabled, go to
   Preferences->Desktop Preferences->Display->Theme

Notice that the Theme Preferences window appears and that 
it is announced as : 
"Create window Theme Preferences,
 Create tab Controls,
 Table Theme Selection Tree [this line isn't always spoken]
 Theme Selection Tree Table "

That's maybe too much information. However, what it doesn't say is the
currently selected table line.

Press the <down> key and you will hear "theme selection tree table"
again, instead of the next line of the table. Pressing <up> or
<down> again causes the currently selected line to be spoken, though.
Comment 1 Dana Ormenisan 2005-01-13 09:42:45 UTC
There are two issues here:
1. The currently selected line (the first line in the table) is not reported
when 'Theme Preferences' window appears: this is a duplicate of bug #163791
(there is no SPI_STATE_FOCUSED cell in that table).

2. After pressing <down> key the second line of the table is not reported.
Instead of reporting the current table line, gnopernicus reports "theme
selection tree, table": this is happening because there is no
'object:active-descendant-changed' at-spi event fired when the second line is
selected.  
If the first line is the current line of the table and user hit <down> all we
receive from at-spi are:
  "object:selection-changed" for 'table'
  "object:visible-data-changed" for 'table'
These events should be followed by an "object:active-descendant-changed" event
in order to have the description of the current line. 
The lack of this event is present only if user moves from 1st line to 2nd line.
If user moves back to 1st line (hit <up>) or forward to 3rd line (hit <down>)
this event is fired and gnopernicus outputs the description for the current
table line.
Comment 2 Dana Ormenisan 2005-01-13 10:08:05 UTC
Bug #163915 was fired for the second problem.
 


*** This bug has been marked as a duplicate of 163791 ***