| Summary: |
PrintPreviewControl: "Printing" frame is no longer showing, but still has "active" state |
| Product: |
[Mono] UI Automation
|
Reporter: |
Brian Merrell <bgmerrell> |
| Component: |
Winforms - General | Assignee: |
E-mail List <mono-a11y-bugs> |
| Status: |
VERIFIED
INVALID
|
QA Contact: |
E-mail List <mono-a11y-qa> |
| Severity: |
Normal
|
|
|
| Priority: |
P3 - Medium
|
|
|
| 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:
|
---
|
|---|
PROBLEM STATEMENT The printpreviewcontrol.py sample application window is an accessible frame named "PrintPreviewControl control". A button (labeled "Button") is on the sample application that loads the PrintPreviewControl. When the PrintPreviewControl is shown, a "Printing" frame appears momentarily and then disappears. Even though the frame disappears the frame accessible still exists. As expected, the accessible of the frame that disappears does not have the "showing" or "visible" states. The problem is that it does have t he "active" state even though the frame isn't even showing. Additionally, the main application frame (i.e., the "PrintPreviewControl control" frame) is active but does not have the "active" state. REPRO 1. Run uia2atk/test/samples/printpreviewcontrol.py 2. Run the attached pyatspi script and follow its directions. The script does the following: 1. Asks you to click the title bar of the printpreviewcontrol.py application window 2. Print the states of the "PrintPreviewControl control" frame, which is the main frame when the application runs. All the states are correct here. 3. Clicks on the "Button" button, which opens the PrintPreviewControl. Notice that a "Printing" window appears very briefly when the preview is loading; this is the "Printing" frame accessible. 4. Print the states of the "PrintPreviewControl control" frame again. 5. Print the states of the "Printing" frame accessible RESULTS The "Printing" frame accessible has the "active" state and the "PrintPreviewControl control" frame does not. EXPECTED RESULTS The main application "PrintPreviewControl control" frame should have the "active" state and the "Printing" frame should not.