Hi Greg Schnider,
I did some experimentation using this code:
What I found is that everything works as expected
as long as I don't set a breakpoint after the NavigateTo call. If I set a breakpoint at MouseHover (for example), then when the breakpoint is hit, input focus is automatically taken away from the browser by Windows and given to Visual Studio so you can interact with Visual Studio. This makes everything break in the code after the breakpoint. You would have to add code to give focus back to the IE browser window after the breakpoint for it to start to work properly again.
Also, from your code sample, the WaitUntilReady and RefreshDomTree are redundant. The NavigateTo step does this automatically.
Greetings,
Cody
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the
Telerik Public Issue Tracking system and vote to affect the priority of the items.