Bug 506159

Summary:	DateTimePicker spin button accessibles erroneously implemented the EditableText interface
Product:	[Mono] UI Automation	Reporter:	Brian Merrell <bgmerrell>
Component:	Winforms - General	Assignee:	E-mail List <mono-a11y-bugs>
Status:	VERIFIED WONTFIX	QA Contact:	E-mail List <mono-a11y-qa>
Severity:	Normal
Priority:	P4 - Low
Version:	Unspecified
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 20:36:32 UTC

PROBLEM STATEMENT

The DateTimePicker accessible has two spin button children. One of the spin buttons represents the day of the month and the other represents the year. Both of these spin button accessible implemented the EditableText interface, but don't appear to be editable in the sense that you can edit the text. (The text is replaced however when a date is selected on the MonthCalendar that drops down, but I am assuming that requires the EditableText. I could be wrong!)

REPRO

1. Run Accerciser, open the "Interface Viewer" tab and expand the "Text (not implemented)" expander
2. Run uia2atk/test/samples/datetimepicker_dropdown.py
3. In Accerciser, browse to and select either of the "spin button" children of the datetimepicker_dropdown.py (ipy) application.
4. Notice that the "Text (not implemented)" text on the interface viewer has changed to "Text (Editable)"
5. Click in the "Text" text area of in Accerciser's interface viewer and edit the value (which can be different depending on which spin button you selected in step 3) to whatever you would like.

RESULTS

The text value of the spin button on the GUI does not change

EXPECTED RESULTS

Because the text value of the spin button doesn't change on the GUI, I would expect the EditableText interface to not be implemented at all.

COMMENTS

This is similar to Bug 468337

The bridge functional spec does specify that spin buttons are editable, but it doesn't seem to make sense in this particular situation. Please, someone correct me if I'm wrong.

Comment 1 Brian Merrell 2009-05-21 20:58:09 UTC

Okay, I suspected this might have been the case, but it looks like this has already been addressed by brad in the 5th comment of Bug 471330.  It reads in part:

"I can't create a Spinner that implements Atk.Action, Atk.Value and Atk.Text but not Atk.EditableText.  This is partly a limitation of Atk+/# and partly a
limitation of our overall design."

So, I will close this as WONTFIX also.