Note also that I recently added defensive code to default.py:onNameChanged to handle multiple name change events for objects whose names are not really changing.  It may have a positive impact on this bug.

OK - we're doing much better with the gail patch for the blocking bug and the defensive name changed stuff in Orca.  However, we're now getting the "Location:" information spoken twice: once for when the text entry area first gets focus and then when the location label issues a state-changed event for showing.

There's special code in Orca to explicitly speak the item with focus if it's label issues a state-changed event for showing, so I'm not sure we can rip that out.  We may be able to rip it out (regression tests would help...), but I'm not certain at this point.

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.

Unblocking this since the blocking bug has been marked as FIXED.

Created attachment 111367 [details] [review]
Revision #1.

Added an onStateChanged() routine to the nautilus script.

If we've received an "object:state-changed:showing" event for the
poorly named gtk-edit toggle button, then just return. We will have
spoken the information for this component with the previously
received "object:state-changed:focused" event. 

For all other events, just let the parent class handle it.

Please test.

Seems to work nicely.  Thanks!  If you can backport this to GNOME 2.22 it would be great, too.

Created attachment 111743 [details] [review]
Same patch for GNOME 2.22.

Both patches committed. Moving to "[pending]".