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 490447 - Can not change status in Pidgin
Can not change status in Pidgin
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-26 09:06 UTC by Javier
Modified: 2007-12-01 01:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Javier 2007-10-26 09:06:46 UTC
Please describe the problem:
Recently discussed in the mailing list (http://mail.gnome.org/archives/orca-list/2007-October/msg00264.html)
In the main window of Pidgin application there is a toggle button to set status mode that can be away, here, not present etc.
This possible list of status only can be displayed if you click the toggle button with mouse.

Pressing space bar or enter key for activating the button it doesn't show the status choices.
Also the toggle button doesn't offer a label or accessible name or description that indicate it's operation.


Steps to reproduce:
1. Start Orca and the pidgin application.
2. Initially you are in the contact list table. Tab key once to get to the status toggle button.
3. Orca says that there is a toggle button and its status unchecked or checked but no label or name with it.
4. Press space to toggle the button. A list of possible status choices should appear.
5. Click this toggle button with the mouse. The list appears.


Actual results:
The list with the status choices doesn't appear.

Expected results:
A list with possible status appears and you can select one.

Does this happen every time?

Yes

Other information:
Using Pidgin 2.2.1 GNOME 2.20
Comment 1 Javier 2007-10-26 09:09:26 UTC
This bug has been initially blocked until Pidgin solves this issues 
The Pidgin ticket is: http://developer.pidgin.im/ticket/3711
Comment 2 Willie Walker 2007-10-26 12:52:42 UTC
Thank you for filing these bugs.  Sorry it took me a while to look into 
this.  What I'm seeing is this on my GNOME 2.20.0 system with Pidgin 
2.1.1:

 * The status setting looks like a combobox, but is actually a 
   toggle button pretending to be a combobox.

 * When you tab to the toggle button, Orca just presents that
   you are on an unpressed toggle button.

 * Pressing the space or return key will pop up the status options.
   You can press up/down arrow and Orca will read the items as they
   are highlighted.

 * Pressing the return key will select a status option for you and
   dismiss the list of status options.

So, aside from being rather kooky in how they chose to use a toggle
button to implement a combobox, I think the main problem we have
here is that the toggle button doesn't seem to be appropriately
labeled.
Comment 3 Joanmarie Diggs (IRC: joanie) 2007-10-26 13:32:31 UTC
It works in Solaris (2.1.1) but it's broken in Ubuntu now (2.2.1). :-(  There, when I press Space or Return on the toggle button/combobox nothing happens, whether Orca is running or not.
Comment 4 Joanmarie Diggs (IRC: joanie) 2007-10-26 14:06:34 UTC
I just got the latest version of pidgin (2.2.2) from sf and things also work as expected.  So either it's broken in 2.2.1 proper and now fixed, or the distro broke it.
Comment 5 Joanmarie Diggs (IRC: joanie) 2007-10-26 14:52:31 UTC
And the winner is:  The distro.  Not sure where they broke it, but pidgin 2.2.1 proper (from sourceforge) also works as expected.

I found this bug already filed in launchpad: 
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/154816
Comment 6 Willie Walker 2007-10-30 15:08:00 UTC
Just assigning this to Joanie so she can be the person to track the blocking bug.
Comment 7 Joanmarie Diggs (IRC: joanie) 2007-11-12 19:31:55 UTC
Update:  Pidgin 2.2.2 hit Hardy today and I can confirm that the reported problem is fixed there.  Rich just confirmed that the upgrade is NOT a part of Gutsy. :-( (Thanks for checking Rich!)  Therefore, I've just added a comment to the launchpad bug (https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/154816) requesting that this update also be included in Gutsy and subscribed the a11y folks to the bug.  I also dropped a note to Luke for good measure. <crosses fingers>
Comment 8 Joanmarie Diggs (IRC: joanie) 2007-12-01 01:31:12 UTC
Given that this bug:

  * Is unique to one version of one distro (Gutsy)
  * Has been fixed by that distro (Hardy)
  * Has a pending backports request for Gutsy users (thanks to Luke)
  * Can be worked around by getting Pidgin from sourceforge
  * Cannot be "hacked around" "in the meantime" by us

I'm going to close this out as NOTGNOME.  If anyone objects, feel free to reopen.