|
Bugzilla – Full Text Bug Listing |
| Summary: | ToolStripDropDownButton: menu with wrong "selected" state | ||
|---|---|---|---|
| Product: | [Mono] UI Automation | Reporter: | calen chen <cachen> |
| Component: | Winforms - General | Assignee: | E-mail List <mono-a11y-bugs> |
| Status: | VERIFIED DUPLICATE | QA Contact: | E-mail List <mono-a11y-qa> |
| Severity: | Normal | ||
| Priority: | P2 - High | ||
| Version: | Release 0.9 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
calen chen
2008-12-16 08:23:29 UTC
Because of #457990, ToolStripDropDownButton no longer can be focused, so part of this bug has been resolved. When it comes to the selection, it seems like the real underlying problem is what is described in #459332 -- that both menus can be open at the same time. This cannot be done as a user, so I don't think you should be able to do it via UIA. Marking this bug as a duplicate of #459332. Work on this issue will continue there. *** This bug has been marked as a duplicate of bug 459332 *** hello brad, i think there is a little bit difference, say sorry that the previous description is complicated. please forget "focused", just look at "selected" state. step 1: run uia2atk/test/samples/toolstripdropdownbutton.py step 2: run accerciser, select toolstripdropdownbutton1 with menu role from left tree, see states step 3: mouse click toolstripdropdownbutton1 in gui window to show menu item list, rise "selected" state is correct step 4: mouse click blank space or move mouse to toolstripdropdownbutton2(don't click) in gui to close toolstripdropdownbutton1's menu item list, then see toolstripdropdownbutton1's states the problem is: in step 4, toolstripdropdownbutton1 still with selected my expectance is get rid of "selected" when menu item list disappear like gtk.menu. please tell me your idea if you have different opinion, thanks :) Yes, you're correct -- I can reproduce the steps you have in comment #2. However, these steps are different than the one in the original bug, so it really needs to be filed as another issue. Closing as duplicate again. The new issue is #463814. *** This bug has been marked as a duplicate of bug 459332 *** I think the different steps both produced one issue :) but it's okay, thanks you created a new bug, it looks more clearly:) Colsed in trunk r122613 |