Error occured in IE 8
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; IPMS/E040400A-14E2CBD58A8-000000501208; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3)
Timestamp: Mon, 25 Jul 2011 04:39:36 UTC
lines: 2979
Char: 5
Code: 0
URI: file:///C:/Users/sosiman/Desktop/sockets/socket.io.js
This line is "req.open(method || 'GET', this.prepareUrl() + '?t' + (+ new Date));"
WARNING: web-socket-js doesn't work in file:///... URL unless you set Flash Security Settings properly. Open the page via Web server i.e. http://...
It's find works in FF, chrom
But IE8 did't work
Any ideas how to fix that?
Thanks!
It's because you are testing it from your local drive, and IE doesn't allow that, so serve that page over a server and the error should disappear
Related
I have seen similar questions in SO but they don't exactly point to the same problem I am facing.
I have two different desktops with same OS (Windows 8) and same version of IE (11.0.9600).
I am trying to connect to the same URL from these two desktops.
However, I notice that two different user-agent values are being submitted from these two IEs.
User-Agent Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; Touch; rv:11.0) like Gecko
and
User-Agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.3; WOW64; Trident/7.0; Touch; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; InfoPath.3; Tablet PC 2.0)
Can someone please help me understand how do I figure out the reason for this?
This issue has implication for me as the portal I am trying to access does not allow the first user-agent value and shows "unsupported browser" message.
Look at the User-Agent, in the second you have "compatible".
This compatible mode on F12 and its run with Explorer 10 user agent.
You are in the compatibility mode in the second instance.As IE is installed along with your windows, it may have been configured automatically in that mode.
I am using SignalR on my project.It is working fine with mozilla and google chrome.When I load the page.During loading error message is shown in IE developer tool. The error is
'$.signalR.transports' is null or not an object connect?transport=foreverFrame&connectionId=f233ca33-962e-4b47-9ec4-f4398fda38d0&connectionData=%5B%5D&frameId=1, line 5 character 9.
Also in error popup this message shown
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.2)
Timestamp: Fri, 4 May 2012 06:06:17 UTC
Message: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)
Line: 0
Char: 0
Code: 0
URI: http://127.0.0.1:81/AddItem/AddItem?CourseItemID=0&CourseID=9976&SystemObjectName=Discussion&IsCourseHomePage=1
Think that you may need the json2.js file. See here?
http://lostinthegc.blogspot.com/2011/09/signalr-doesn-work-in-ie-internet.html
I am very new in using ActiveX controll through java script,
I write var f = new ActiveXObject('Scripting.FileSystemObject'); in my code and Its was working fine on IE6, but recently I upgraded my IE6 to IE8 and what I found now its not working on IE8, returning the error given below:
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; MS-RTC LM 8;
.NET4.0C; .NET4.0E; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Wed, 31 Aug 2011 14:23:40 UTC
Message: Automation server can't create object
Line: 735
Char: 9
Code: 0
URI: http://localhost:8080/
qocweb/script/main/MainLetter.js
I googled this and found there is something missing in the IE ActiveX setting and got resolved this problem,
But now I have a requirement that it should be solved without playing with IE8 setting.
Can anyone have any idea about this, any suggestion would be really appreciable...
You can not use this component with default security settings due to security reasons. Read this for more information.
I just upgrated from VS2005 to VS2010 and works fine except for the following error on IE8 only:
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0;
.NET CLR 1.1.4322; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR
2.0.50727; yie8) Timestamp: Tue, 16 Aug 2011 18:46:04 UTC
Message: ASP.NET Ajax client-side framework failed to load.
Line: 130
Char: 34
Code: 0
URI: http://...
Message: 'Sys' is undefined
Line: 15
Char: 1
Seems like the the ScriptResource.axd js is not loaded correctly most of the time on this browser.
I've researched a lot about this kind of error and tried several things without luck. The wreird thing is that it's happenning just on IE8. Chrome and Firefox work fine.
It also works fine sometimes on IE8 :S
I din't find a conventional solution for this problem.
After debugging it I noticed that the problem was that the ajax script resources where loading after some other scripts.
I was not able to move the sripts up in the page because the application is very old and it wasn't even using master page, so I was limited on that.
I researched about the script manager and I found a new property on asp.net 4.0 called EnableCdn that basically, if it's set to "true", it loads the resources from the Microsoft content resource servers. Doing that those scripts loads quicker and the errors disappeared.
I hope this experience be useful for someone else.
Thanks!
I'm kind of lost with how IE8 determines the document mode. I got contradictions.
Setup
This is what a generated web page header looks like on my website, please note the doctype:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="Head">
<meta id="IE8" http-equiv="X-UA-Compatible" content="IE=8" />
...
I'm using the meta http-equiv setted to X-UA-Compatible to force it to render in "standard mode", because this website has been made so. The website is on another machine in the company LAN (10.1.x.x).
Everything is ok up to now, but I'm having difficulties with the compatibility settings window:
Results:
When nothing is checked and listed in compatibility settings, user agent is:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) [ok]
When only "Display all websites in Compatibility View" is checked:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) [coherent but not expected]
When only "Display intranet sites in Compatibility View" is checked:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) [not ok]
When the URL is added to the list of "Websites you've added to Compatibility View":
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) [coherent but not expected]
According to the following IE blog entry diagram, if the meta tag X-UA-Compatible is present and value is IE=8, the renderer is setted to "Standards mode".
As just described, that is not the case. Meta was always IE=8 but the user agent changed.
The diagram takes care of the compatibility view settings after the X-UA-Compatible meta check. In my case, it looks like the opposite.
Is the diagram wrong?
Questions:
Why the user agent is msie 8.0 when "Display intranet sites in Compatibility View" is checked?! (is it because of my meta? Is http://10.1.x.x/ really considered as an intranet website?)
Why the user agent is msie 7.0 when "Display all websites in Compatibility View" is checked??? (this override my meta ? but not according to diagram)
Why the user agent is msie 7.0 when the site is added to the compatibility list ?
According to the diagram, my doctype falls in the "Almost Standards Mode" category.
Seems there's a better meta to force IE8 standard mode, but according to the doctype:
<meta id="IE8" http-equiv="X-UA-Compatible" content="**IE=EmulateIE8**" />
Is it better to use it, or the one I'm currently using (force IE=8)?
Seems Almost Standards Mode is exactly the Standard Mode with a subtle change for the rendering of images in a table, ok but... which one should I pick?
Then again the diagram mention "IE=Emulate8" but this article talks about "IE=EmulateIE8", seems like the later is the correct version according to the documentation of http-equiv.
Is there a way to detect (client side/network) if IE is in "Almost Standards Mode" or "Standards Mode" ?
A few links worth mentioning:
http://blogs.msdn.com/b/ie/archive/2008/08/27/introducing-compatibility-view.aspx
http://blogs.msdn.com/b/ie/archive/2009/02/16/just-the-facts-recap-of-compatibility-view.aspx
http://msdn.microsoft.com/en-us/library/ms533876(VS.85).aspx
http://msdn.microsoft.com/fr-fr/library/cc288325(VS.85).aspx
http://blog.strictly-software.com/2009/03/detecting-ie-8-compatibility-modes-with.html
http://phrogz.net/ie8-intranet-compatibility-view
http://hsivonen.iki.fi/doctype/ -> http://hsivonen.iki.fi/doctype/ie8-mode.png
javascript:alert(navigator.userAgent)
javascript:alert(document.compatMode);
javascript:alert(document.documentMode);
IE Dev tools indicate which rendering engine is being used.
Don't rely on the User Agent string to determine the rendering engine.