Bug 504593

Summary:	Button does not receive focus when click action is performed on it
Product:	[Mono] UI Automation	Reporter:	Brian Merrell <bgmerrell>
Component:	Winforms - General	Assignee:	E-mail List <mono-a11y-bugs>
Status:	REOPENED ---	QA Contact:	E-mail List <mono-a11y-qa>
Severity:	Major
Priority:	P3 - Medium	CC:	cachen
Version:	Release 1.0
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 11.1
Whiteboard:
Found By:	Integration Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Brian Merrell 2009-05-17 08:46:35 UTC

PROBLEM STATEMENT

The bridge functional spec[1] indicates that when a click action is performed on a button that that button should then gain the focused state.  However, that is not currently the case.

REPRO

1.  Run Accerciser, open the "Interface Viewer" tab, and expand the "Accessible" and the "Action" expanders.
2.  Run uia2atk/test/samples/button_label_linklabel.py
3.  In Accerciser's left pane, browse to and select the "button2" push button accessible of the button_label_linklabel.py (ipy) application
4.  Under the "Action" expander, in Accerciser's interface viewer, select the "click" action and then press the "Perform action" button.
5.  Click on the button_label_linklabel.py title bar

RESULTS

After step 4, the "You have clicked me <n> times" label changes on the sample application, indicating that the button has been clicked.  Step 5 activates the application frame so that the button2 push button accessible should have the focus state.  However, you will see in the "States" list (under the "Accessible" expander) in Accerciser's interface viewer that it does not.

EXPECTED RESULTS

The "button2" push button accessible should receive the "focused" state.

COMMENTS

I have verified the expected results in Gtk+ (using the gtkbutton.py sample application)

[1] http://mono-project.com/Accessibility:_Bridge_Functional_Specification

Comment 1 Brian Merrell 2009-05-17 08:53:27 UTC

The "button1" and "button2" buttons on button_label_linklabel.py receive a red outline when they are navigated to using the keyboard.  This outline should also appear when using the click action if at all technologically possible :) 

I actually encountered this issue while working on the ColorDialog test and clicking on the little color boxes (which appear as push button accessibles).  We should make sure the focus state is gianed by these ColorDialog accessibles before closing this bug.

Comment 2 Andres Aragoneses 2009-07-01 21:15:43 UTC

(In reply to comment #0)
> I have verified the expected results in Gtk+ (using the gtkbutton.py sample
> application)

You sure?

Steps:
1. open gtkbutton.py
2. open accerciser.
3. in accerciser, go to event monitor-> mark Selected Accessible, click on Select All.
4. in accerciser left pane, click on button2.
5. in accerciser, click Monitor Events, now go to Interface Viewer -> Action.
6. Click on "click" element and "Perform action", go back to Event Monitor.

Current results:
No focus events appeared.

Comment 3 Brian Merrell 2009-07-01 22:40:39 UTC

I never didn't notice this before but the Gtk+ behavior differs between my openSUSE 11.0 machine (that doesn't our our stuff installed) and my openSUSE 11.1 machine that does have our stuff installed.  The openSUSE 11.1 (GNOME 2.24) machine does change the focus when clickable widgets are clicked (I have at least tested buttons and check buttons).  The openSUSE 10.1 has the behavior your described in Comment #2.  I am not sure exactly what causes the difference in behavior; I can look into it further if you'd like.

Comment 4 Andres Aragoneses 2009-07-02 15:30:52 UTC

Thanks for the info Brian.

However, given the special circumstances, I think we can agree that this is not so important, so am lowering the appropriate field.