482571 – ToolBarButton can be navigated to (focused) but cannot be invoked with the keyboard

Bug 482571 - ToolBarButton can be navigated to (focused) but cannot be invoked with the keyboard

Summary: ToolBarButton can be navigated to (focused) but cannot be invoked with the ke...

Status:	RESOLVED DUPLICATE of bug 509985

Alias:	None

Product:	Mono: Class Libraries
Classification:	Mono
Component:	Windows.Forms (show other bugs)
Version:	SVN
Hardware:	Other Other

Priority:	P5 - None Severity: Minor
Target Milestone:	---
Assignee:	Mono Bugs
QA Contact:	Mono Bugs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2009-03-05 20:25 UTC by Andres Aragoneses
Modified:	2009-06-04 15:45 UTC (History)
CC List:	1 user (show)

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

Attachments
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 Andres Aragoneses 2009-03-05 20:25:34 UTC

Steps to reproduce:
1. Launch this sample app: http://anonsvn.mono-project.com/viewvc/trunk/uia2atk/test/samples/toolbarbutton.py?view=log
2. Press the down-arrow of your keyboard: now you can focus on the toolbarbuttons.
3. Move to the first or the last "nop" element, and press Enter on them.

Current results:
Nothing happens. (Mono)

Expected results:
The label below should be changed to "You clicked nop button" or "You clicked PushButton X times". (MS.NET)

Comment 1 Carlos Alberto Cortez 2009-05-23 16:49:28 UTC

The iron python sample is not working for me (at least on Linux with the last IronPython version). Unfortunately it's not showing error message, and it just basically doesn't show any form.

Running with trace activated shows a ImportException, which sounds like there's something wrong with the import statements, or with the references. 

Any chance to take a look at that?

Comment 2 Brian Merrell 2009-06-04 15:45:06 UTC

Sorry Andres, I didn't see that you had already logged this bug.  I just logged a new one, but I think it provides some additional information.

Carlos, the problem was that the sample that Andres linked had some code that relied on our specific test environment.  I will correct this in Bug 509985.

*** This bug has been marked as a duplicate of bug 509985 ***