Bug: Ctrl-N in Unit Test Runner launches IE.


Subject says it all. Hitting Ctrl-N while in the Unit Test Runner
launches IE instead of executing the bound command.

2 comments
Comment actions Permalink

You must have had focus on IE.



"Casey Barton" <a@b.com> wrote in message
news:oh5go2prr6cu3op1f364om43stngstqfm7@4ax.com...
>

Subject says it all. Hitting Ctrl-N while in the Unit Test Runner
launches IE instead of executing the bound command.



0
Comment actions Permalink

On Tue, 19 Dec 2006 09:42:44 -0800, "Jake" <jsmith@aristocrat-inc.com>
wrote:
>"Casey Barton" <a@b.com> wrote in message
>news:oh5go2prr6cu3op1f364om43stngstqfm7@4ax.com...
>>
>> Subject says it all. Hitting Ctrl-N while in the Unit Test Runner
>> launches IE instead of executing the bound command.
>
>You must have had focus on IE.

This happens when focused on VS, but I realize now that you're half
right.

The issue is that the unit test runner is using embedded IE to display
the results, and so it starts grabbing all the events. What a pain!

Is there anything that can be done about this? It's messy, because
there are definitely keyboard events (like tabbing through source
links in stack traces) that you want to leave intact.

- Casey

0

Please sign in to leave a comment.