Bug 511166 - TabPage:from Accerciser can't see the inactive "page tab"'s children
Summary: TabPage:from Accerciser can't see the inactive "page tab"'s children
Status: VERIFIED INVALID
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - ATK (show other bugs)
Version: Release 1.0
Hardware: i686 openSUSE 11.1
: P3 - Medium : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-09 08:41 UTC by Feng Xia Mu
Modified: 2009-06-09 10:17 UTC (History)
0 users

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

Attachments
the output of step 3 (113.47 KB, image/png)
2009-06-09 09:05 UTC, Feng Xia Mu 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Feng Xia Mu 2009-06-09 08:41:45 UTC 
SUMMARY

run tabpage.py example,if "page tab" accessible is not the current active page, it's children can't be got from Accerciser, maybe it's Accerciser 's bug, I'm not sure and hope more advices.

REPRO

1.  run uia2atk/test/samples/tabpage.py, 
2.  run accerciser, expand the item with 'page tab list' role name  from left pane of Accerciser
3.  try to expand all the "page tab"
4.  on sample GUI, click "Tab 1" to make it the current active tab.

RESULTS

step 3: only "Tab 0" can be expanded.
step 4: "Tab 1" can be expanded, "Tab 0" can not be expanded

EXPECTED RESUlt

step 3: all the "Tab" with "page tab" role name should be expanded
step 4: both "Tab 1" and "Tab 0" can be expanded
Comment 1 Feng Xia Mu 2009-06-09 09:05:05 UTC 
Created attachment 296887 [details]
the output of step 3
Comment 2 Feng Xia Mu 2009-06-09 10:17:01 UTC 
from bug 464356, Comment #4 released by Brad,
"This deviates from GAIL's behavior a bit, but we really had no choice.  Only
when a tab is selected are its children shown -- this needed to be done to
reflect what Vista is doing on the provider side."

I think this bug won't need to open.