>I think it might be possible to use the keyboard to go to the "next" page, .Click() wouldn't fire there either. Fast computer users use keyboard shortcuts/hotkeys etc.
>
>If it were up to me I'd put the code in .Activate(), it most closely describes where you want the code to run. However you get to that page, all paths lead to .Activate() so you don't have to worry about exactly how you got there. Putting code in .Click() instead just feels like something that would bite me later on.
>
Solid reasoning, still "Events should call Methods" ;-)
Implementing the "FixActivateIssues" in a method, that method might be called from different events, perhaps with checking in advance