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 509834 - Orca should speak the new folder with focus as it appears
Orca should speak the new folder with focus as it appears
Status: RESOLVED DUPLICATE of bug 486908
Product: orca
Classification: Applications
Component: general
2.21.x
Other All
: Normal normal
: 2.22.0
Assigned To: Rich Burridge
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-16 06:15 UTC by Mike Pedersen
Modified: 2008-07-22 19:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
Orca debug generated whilst running this test. (85.92 KB, text/plain)
2008-01-16 17:21 UTC, Rich Burridge
Details

Description Mike Pedersen 2008-01-16 06:15:30 UTC
1.  Open your home directory in nautilus in list view.
2.  notice that the folder that gains focus is not spoken 
3.  down arrow to a folder and press enter
4.  again notice that the new folder with focus isn't spoken.
I would expect the folders that gain focus to be spoken followed by "not selected".  I would also expect the file/folder name to appear in braille.
Comment 1 Rich Burridge 2008-01-16 17:21:55 UTC
Created attachment 103006 [details]
Orca debug generated whilst running this test.

Commentary to follow...
Comment 2 Rich Burridge 2008-01-16 17:22:57 UTC
Summary: this is basically the crux of bug #486908. The difference
between a list item being selected and it being focused (or both).

Here my evaluation in more detail.

> 1.  Open your home directory in nautilus in list view.

At the "window:activate" event the following is spoken (line 169):

SPEECH OUTPUT: 'richb - File Browser frame'

> 2.  notice that the folder that gains focus is not spoken 

Initially the focus is not on any specific folder in the list. It's on
the table. See line 192.

The following is also spoken (line 241):

SPEECH OUTPUT: ''
SPEECH OUTPUT: 'List View table'

> 3.  down arrow to a folder and press enter

Arrowing down causes the following to be spoken (line 388):

	SPEECH OUTPUT: ''
SPEECH OUTPUT: 'Name column header'
SPEECH OUTPUT: 'applications collapsed'
SPEECH OUTPUT: 'tree level 1'

"applications" is the name of my first folder in my home directory.

(Mike, you do have the latest gail from SVN trunk installed don't you?
You'll need that for the fixes to bug #497218 and bug #508255)

> 4.  again notice that the new folder with focus isn't spoken.

Pressing Return (line 452) causes the following events:

---------> QUEUEING EVENT object:property-change:accessible-name
---------> QUEUEING EVENT object:selection-changed
---------> QUEUEING EVENT object:state-changed:showing  (dozens of them)
---------> QUEUEING EVENT object:property-change:accessible-name
---------> QUEUEING EVENT object:property-change:accessible-value
---------> QUEUEING EVENT object:property-change:accessible-name (6 of them)
---------> QUEUEING EVENT object:property-change:accessible-value
---------> QUEUEING EVENT object:property-change:accessible-name
---------> QUEUEING EVENT object:property-change:accessible-value
---------> QUEUEING EVENT object:property-change:accessible-value

Processing the "object:property-change:accessible-name" event (line 996)

OBJECT EVENT: object:property-change:accessible-name   detail=(0,0)
    app.name='nautilus' name='applications - File Browser' role='frame' state='active enabled resizable sensitive showing visible' relations=''

causes the following to be spoken (line 1523):

SPEECH OUTPUT: 'applications 7 items'

Note that none of the entries in the file list currently have focus.

Pressing Down (line 1653) causes the following events:

---------> QUEUEING EVENT object:selection-changed
---------> QUEUEING EVENT object:active-descendant-changed
---------> QUEUEING EVENT object:property-change:accessible-name
---------> QUEUEING EVENT object:text-changed:delete
---------> QUEUEING EVENT object:text-changed:insert
---------> QUEUEING EVENT object:property-change:accessible-name

Processing these events do not cause anything to be spoken.

Looking at the nautilus components with accersizer, we can see that
the first entry in the listed is selected (visually it's blue), but
it's not focused. The focus is still with the table. The focus hasn't
changed so nothing new is spoken.

So, in order to fix this, we need to decide what should be spoken
when an item is selected but does not have focus. That is bug #486908.
Perhaps this is another test case that should be added to that bug.

Pressing Down again (line 1732) causes the following events:

---------> QUEUEING EVENT object:selection-changed
---------> QUEUEING EVENT object:property-change:accessible-name
---------> QUEUEING EVENT object:text-changed:delete
---------> QUEUEING EVENT object:text-changed:insert
---------> QUEUEING EVENT object:property-change:accessible-name
---------> QUEUEING EVENT object:active-descendant-changed
---------> QUEUEING EVENT object:property-change:accessible-name

Processing the "object:active-descendant-changed" event (line 1795) 
causes the following to be spoken (line 1849):

SPEECH OUTPUT: ''
SPEECH OUTPUT: 'gmp-4.2.2 collapsed'

Looking at the components with accersizer again, we can see that that
second list entry is not only selected but it is now focused as well
(which is what causes something to be spoken -- the focus has changed).

So, should I be filing a bug against nautilus for inconsistent behaviour?
I.e., if you down arrow into the list, should that first item be selected
and focused (because that's what happens when you Down arrow again).

Should I add this test case to bug #486908, for something else that Mike
needs to spec out for what should be spoken/brailled?

Should I also then just close this as a duplicate of bug #486908?
Comment 3 Willie Walker 2008-01-16 18:47:23 UTC
This seems it may indeed be a duplicate of bug 486908 and this might be yet another test case.  Mike, please go through the test cases outlined in bug 486908 and provide the feedback that's been requested.
Comment 4 André Klapper 2008-01-16 20:23:44 UTC
/me wonders if the GNOME target was set by purpose and cannot judge the importance of this bug
Comment 5 Willie Walker 2008-01-16 20:40:08 UTC
Sorry - yep.  I believe that was a mistake.  :-(
Comment 6 Rich Burridge 2008-01-16 23:19:36 UTC
Closing as a duplicate of bug #486908. I'll add this test case
as a comment to that bug. Thanks Will.


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