>Its possible that it could be fixed in an update, but Windows Server 2003 would be 10 years old now, and may only be receiving security updates (http://support.microsoft.com/lifecycle/default.aspx?LN=en-us&x=11&y=8&p1=3198). This update may correct the issue (see issue 2): http://support.microsoft.com/kb/2836939. If you can't control or update the server, the browser file would be an alternative.

It is mostly Windows Server 2008. I only have one server remaining in Windows Server 2003.

The browser file is nice. It would allow to workaround that issue. However, the thing with that is when it would be fixed at the browser level, we wouldn't have any way to know about it and remove the browser file. So, this would remain a dependency on the application and we would never know if it is still needed or not.

>With Web Forms, the server uses the browser files to determine what capabilities the user's browser has and adjusts the output based on that. With IE 11, it likely can't determine that javascript is supported and doesn't render the appropriate client side code to focus on the correct element.

That is what I think. I have seen a few issues like that at the very first version of it and it would be interesting to see the first update to it.

>Also, if focus is your only issue and you are using HTML5, you could try setting the autofocus attribute: http://www.w3schools.com/tags/att_input_autofocus.asp

That is interesting. Yes, I have converted all applications to HTML5. So, I will check for that.

Thanks