Ah! Thanks so much for this post. ASP.NET's insistence on a single server-side form per page is a bit of a bugbear of mine. Clearly this results in the annoying focus on the first button on the page whereas in olden days you'd have several (client-side) forms and the first button on the *form* that was focussed would get the keypress. This is the behaviour that users are likely to expect.
I was about to whip up some needlessly complex jQuery when I stumbled across your post documenting a .NET2.0 feature that I hadn't come across, which has allowed me to keep the default button selection in the C# where I won't lose it!
Thanks again
Jon.
I was about to whip up some needlessly complex jQuery when I stumbled across your post documenting a .NET2.0 feature that I hadn't come across, which has allowed me to keep the default button selection in the C# where I won't lose it!
Thanks again
Jon.