Internet Explorer 10 fails to postback asp command unless it's in compatibility mode
I have a very simple program consisting of three aspx files that receive a login id from another web site and looks up all the accounts in the first drop down using ASP CLASSIC. It fills the first drop down list on the web page just fine. I then click the down arrow on the second dropdown after selecting one of the accounts in the first dropdown and it is supposed to fill the second drop down with all the assests related to the first accountholder. The code works fine in EVERY browser including IE 10 compatibility mode BUT does not work in IE 10 with compatibility mode turned off. I've read that IE 10 fails to recognize pages properly and JavaScript and ASP no longer work. I've also heard that this failure of IE 10 disables the action of doPostBack. I've tried differently suggested meta-tags from Microsoft web sites to no avail. What are my options?
Since it's only 3 web pages, I'm thinking of just rewriting the darn thing. If so, What language will work will overcome this error. From forum posts, it's been going on for nearly a year and my IE 10 has been faithfully automatically updated.
Bob
Since it's only 3 web pages, I'm thinking of just rewriting the darn thing. If so, What language will work will overcome this error. From forum posts, it's been going on for nearly a year and my IE 10 has been faithfully automatically updated.
Bob
ASKER
I can re-create the issue. Can't provide the original due to customer specific wording.
Bob
Bob
ASKER
The first attachment IE10.TXT I've masked any client information. It is the result of IE10 with compatibility OFF.
The second attachment IE10Compatible.txt works and has IE10 Compatible view turned on. The files are quite different. One that works has JavaScript code and the other does not.
Thanks for taking a look at it.
I've removed any private identifying data but thought the best example would come from a real world issue.
IE10.txt
IE10Compatible.txt
The second attachment IE10Compatible.txt works and has IE10 Compatible view turned on. The files are quite different. One that works has JavaScript code and the other does not.
Thanks for taking a look at it.
I've removed any private identifying data but thought the best example would come from a real world issue.
IE10.txt
IE10Compatible.txt
Hi Bob,
thanks, that is really interesting.
Can you please verify / confirm, that you have removed part of the HTML head?
In both files, there is no opening head tag nor the opening title tag. If this is due to your cleanup then fine - if not then it would be a good place to start. I am not sure how IE10 without compatibility reacts especially with this doctype.
Thanks.
Rainer
thanks, that is really interesting.
Can you please verify / confirm, that you have removed part of the HTML head?
In both files, there is no opening head tag nor the opening title tag. If this is due to your cleanup then fine - if not then it would be a good place to start. I am not sure how IE10 without compatibility reacts especially with this doctype.
Thanks.
Rainer
ASKER
I removed a Microsoft suggested meta tag. Possibly took out too little or too much. Here is the only meta-tag I removed that was an attempt to make the browser think it was IE9
<meta http-equiv="X-UA-Compatibl
Bob
<meta http-equiv="X-UA-Compatibl
Bob
ASKER
What doctype would I use or how can I create a page with an acceptable doctype. I have Visual Studio 2010.
I am not a web programmer but with 30 years experience with desktop apps I thought this simple job would be easy using just asp code in notepad. It's been working fine with no errors on every other browsers for months now.
Most likely I'll need to rework in Visual Studio 2010 as asp.net instead of ASP.
Bob
I am not a web programmer but with 30 years experience with desktop apps I thought this simple job would be easy using just asp code in notepad. It's been working fine with no errors on every other browsers for months now.
Most likely I'll need to rework in Visual Studio 2010 as asp.net instead of ASP.
Bob
ASKER
I arrived at the two attached documents by using the same program and getting to same place and then choosing View Source from the right click using the same computer. The only difference was that in one instance it worked because in compatibility mode it recognized the page and without compatibility mode it did not. Therefore when compatibility mode was not on, it did not have access to JavaScript. There was not change in settings or the availability of JavaScript on the client side.
Reviewing internet postings over the last 6 months reveals nothing except vague reference to kb's that are different for the computer being used as a client.
My computer is Windows 7 64 bit with 8 gig of RAM using Microsoft Security Essentials.
Hope someone can find an answer to this increasingly common malady.
Bob
Reviewing internet postings over the last 6 months reveals nothing except vague reference to kb's that are different for the computer being used as a client.
My computer is Windows 7 64 bit with 8 gig of RAM using Microsoft Security Essentials.
Hope someone can find an answer to this increasingly common malady.
Bob
ASKER
I'd read somewhere that there were problems with the local instance of either .net 2.0 and/or .net 4.0. The application is a .net 2.0 application.
Bob
Bob
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
IE 10 compatibility mode fixed the issue
ASKER
IE 10 Compatibility fixed the immediate issue
could you please share the server side code and the resulting HTML/Javascript OR provide a link where we can see the ouput.
The issue could only be on the client side and not on the server.
Thanks.
Rainer