Bug 506252 - DateTimePicker table cell accessibles erroneously implement the EditableText interface
Summary: DateTimePicker table cell accessibles erroneously implement the EditableText ...
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - General (show other bugs)
Version: Release 1.0
Hardware: x86 openSUSE 11.1
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-22 03:58 UTC by Brian Merrell
Modified: 2009-07-02 03:35 UTC (History)
1 user (show)

See Also:
Found By: Integration Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Merrell 2009-05-22 03:58:00 UTC
PROBLEM STATEMENT

The DateTimePicker accessible has two tree table children.  One of these tree tables contains table cells that represent the day of the week (i.e., "Monday", "Tuesday", etc) and the other tree table contains table cells that represent the name of the month.  The problem is that all of these table cell accessibles implement 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 expand either of the "tree table" children of the datetimepicker_dropdown.py (ipy) application.
4.  Select any of the "table cell" children of the "tree table" accessible expanded in step 3.
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 associated text on the GUI does not change

EXPECTED RESULTS

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

COMMENTS

This is somewhat similar to Bug 468337