Bug 505281

Summary:	ComboBox (DropDownStyle = Simple) text field has extraneous "selectable" state.
Product:	[Mono] UI Automation	Reporter:	Brian Merrell <bgmerrell>
Component:	Winforms - General	Assignee:	E-mail List <mono-a11y-bugs>
Status:	NEW ---	QA Contact:	E-mail List <mono-a11y-qa>
Severity:	Normal
Priority:	P4 - Low	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-19 15:46:45 UTC

PROBLEM STATEMENT

A ComboBox with DropDownStyle = Simple has an editable text field above the list of ComboBox elements.  The problem is that this text field accessible has the "selectable" state; I don't believe it should.

REPRO

1.  Run Accerciser, open the "Interface Viewer" tab, and expand the "Accessible" expander.
2.  Run uia2atk/test/samples/combobox_simple.py
3.  In Accerciser's left pane, browse to and select the "text" accessible, which is a child of the "combo box" accessible in the combobox_simple.py (ipy) application.

RESULTS

The list of states in the interface viewer tab shows that the "text" accessible has the "selectable" state

EXPECTED RESULTS

I don't see any reason that the "text" accessible should have the "selectable" state here.

Comment 1 calen chen 2009-07-09 10:35:47 UTC

Hi Brian, in this sample, if selectChild(1) is called from 'combo box', the 'text' accessible is raised 'selected' state, so do we think if the accessible can be 'selected' that it should have 'selectable' state? (bug520567 mention the sample problem for 'tree table'), or perhaps Selection is called from 'combo box' that both 'tree table' and 'text' shouldn't raise 'selected' state, but raise 'selected' for the selected menu_item?

Comment 2 Brian Merrell 2009-07-09 15:39:12 UTC

(In reply to comment #1)
> Hi Brian, in this sample, if selectChild(1) is called from 'combo box', the
> 'text' accessible is raised 'selected' state, so do we think if the accessible
> can be 'selected' that it should have 'selectable' state? (bug520567 mention
> the sample problem for 'tree table'), or perhaps Selection is called from
> 'combo box' that both 'tree table' and 'text' shouldn't raise 'selected' state,
> but raise 'selected' for the selected menu_item?

Yeah, I see no reason for the 'selected' state to be given to the 'text' accessible here, even if selectChild(1) is called from 'combo box'.  The definition of Atk.SELECTED is:

"Indicates this object is the child of an object that allows its children to be selected and that this child is one of those children that has been selected."

I just don't think that applies here.  Maybe it does?