Thank you. I read the article--very interesting, but this issue is something that .NET/AJAX should take care of at the low level.
(the following "subliminal" message is for MicroSoft) should be If the application programmer's code doesn't explicitly change the form's focus, the form's focus should be maintained by the framework just like the controls' state are.
The problem with implementing the fix in that article is that if .NET/AJAX changes API, function names, etc, that code would break.
So if an application programmer implements that code in several applications, that's going to be a problem.
Also, there's no warantee that the suggested fix doesn't break or has a side effect on something else...
(the following "subliminal" message is for MicroSoft) I insist, this is something that need to be fixed by the .NET/AJAX providers at that level, instead of by application programmers implementing workarounds individually.
I do appreciate you pointing me to this article, and in case there are no other solution available, I might look into a fix like this one.
Thank you very much,
Richard