Bug 506082

Summary: DateTimePicker panel accessible should not have "focusable" and "focused" states
Product: [Mono] UI Automation Reporter: Brian Merrell <bgmerrell>
Component: Winforms - ATKAssignee: E-mail List <mono-a11y-bugs>
Status: NEW --- QA Contact: E-mail List <mono-a11y-qa>
Severity: Normal    
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-21 17:21:06 UTC 
PROBLEM STATEMENT

The bridge functional spec[1] shows that a "panel" accessible does not have a "focusable" state.  Additionally, Brad state in Bug 483735 that "as far as I understand is correct -- the DateTimePicker can't be focused, only it's children can."  In spite of this, the DateTimePicker panel accessible have the "focusable" and the "focused" state when the DateTimePicker sample applications are run.

REPRO

1.  Run Accerciser, open the "Interface Viewer" tab, and expand the "Accessible" expander
2.  Run datetimepicker_dropdown.py or datetimepicker_showupdown.py
3.  In Accerciser's left pane, browse to and select the "panel" accessible of the sample application.  This accessible apparently represents the DateTimePicker as a whole.
4.  Click on the sample application's title bar to activate the window
5.  Notice the "States" list for the selected accessible in the interface viewer

RESULTS

The panel accessible has both the "focusable" and "focused" states.

EXPECTED RESULTS

The panel accessible should not have the "focusable" state, which also means that it should not have the "focused" state.

COMMENTS

Again, Bug 483735 might have some relevant information.