My site is http://www.ancientwords.us. I've tried every Javascript troubleshooting tool in the book, but I can't see to figure out why the site isn't loading in IE 8 (or IE7 for that matter).
When using IE10 in IE8 mode, I get a notification that there is a non-responding script, hence why I think it is a Javascript related error. Even still, I haven't been able to find a tool that has been able to tell me what's wrong.
I've tested the site in Safari, FireFox, and Chrome and everything works fine. The site also works fine in IE9 and IE10.
Does anyone have any advice?
Turns out Cloudflare was causing the problem. The Rocket Loader feature is not compatible with older versions of IE.
Did you report the Rocket Loader bug to us?
Related
here i have a react app that has some codes like finally that is not supported in some browsers like IE, Safari and ... (i tested it in BrowserStack)
as you can see it doesn't show anything on IE:
and here we can see the project on firefox
can some one help me to run these codes on unsupported browsers because i really can't change the code it will be so hard to correct it
do you have any suggestion?
Refer to title question. I am very new to javascript and used it while making an html page for work on my laptop that works perfectly fine with Internet Explorer 8, but it does not work on anyone's computer that has installed IE11. As we are all supposed to upgrade to IE11 (nobody told me until this issue came up), I need to figure out why this works in IE8 and not IE11. I am guessing that the XMLHttpRequests are the issue. Basically I am using the xmlhttprequests to check if some files exist before posting them to the html page.
I'm in the process of requesting and getting approved to install IE11, but was hoping someone could clarify if I am correct that XMLHttpRequests do not work in IE11 and could possibly suggest any alternatives?
Edit:
Well magic stuff occurred and now its working.
Short answer: Yes.
Long Answer: Internet Explorer has supported XHR (XMLHTTPResponse) since IE 7. Since then it has improved considerably. There are many things that can stop code from working. Have you tried running your code in IE 11 and then checking the debug console to see what it says?
Unfortunately, since you did not post any code for us to examine; we can't really do much for you except answer your very specific and easily searchable question.
Recommendation: Use jQuery to do AJAX requests instead and examine the debug console for errors.
So i am completely baffled by this and hoping someone can give me some ideas to try. Not sure what details to include so let me know if i dont describe it enough and i'll add more.
We inherited a .Net MVC 4 app from a former company that already has a version on our clients production server. Recently, after a few updates from us, our client noticed that some of the menu items, styling, etc is screwed up on their test and QA servers in IE9 but works on production (Production is still from the previous companies publish). The test and QA versions also work fine in FF and Chrome
Using IETester and IE11, I tried viewing the page in IE9 mode but I did not see the same issues that my client is having, so i tried some older versions out of curiosity. I managed to reproduce the issue, but in IE7 not IE9. I had my client verify that he is in fact using IE9 and he is.
I did a compare with older versions of our _Layout.cshtml and there isnt a single thing that changed other than a favico entry. As far as i can tell, we havent changed any css or styling.
I have a webex meeting with the client tomorrow to look at his IE to see if i can find anything, but can anyone give me some ideas of what could cause this? Particularly that this page works in my IE9 but not his?
sometimes when you set the default browser mode to be ie7 and the document mode to be ie9 standard and you try again to change the browser mode to be ie9 compat view then unfortunately the browser version will be detected as ie7 , the solution for this problem is to change the browser mode to be ie9 but not ie9 compat view then the browser version will be detected as ie9
I am working on a website for a friend. He wants a flash animated style website without any flash so that it works on IOS and he can change things himself. I am using JQuery along with my own javascript, and several css files. Now the problem is the website works perfectly on my internal development server on all browsers. When I uploaded it to my sub domain to show him the progress it no longer works on IE. All other browsers work perfect just not IE and only when its on the internet. I've already gone through the w3 validations with no errors. All java and everything is enabled on IE, I'm stumped. Does this happen to anyone else's IE or is it just on my computer?
Incomplete Demo
Looks like you've got JavaScript errors.
$('div#top').animate ({bottom: '250px', }, timeDuration);
That stray comma makes IE unhappy (even IE9).
Of course that would have caused IE to have problems if you served the page from your local server too.
(Oh wait; my IE is stuck in compatibility mode ... well anyway those stray commas will definitely freak out some versions of IE.)
I am getting a very weird kind of error with IE9. When I use a DOMParser from within a jsp page on localhost, it runs perfectly fine and gives the proper result.
But Shockingly, when I use DOMParser inside a normal HTML file (Not on the server. From the file system), I get this annoying message of "DOMParser is undefined" .. What is this and how can I make it work? Thank You.
P.S. It works fine on FF and Chrome
I would say that this is almost certain to be the browser running in compatibility mode when browsing local URLs.
You can check this by opening the dev tools (press F12) and looking in the top right corner; if it says it's in IE7 mode, then you've found the problem. Switch it back to normal IE9 mode and it should come right.
IE7 didn't support the DomParser object, so if IE9 is in IE7 compatibility mode, it's natural that it will stop supporting it too.
Ok, so that's what it's doing. But why is it doing this? There is a config setting in IE (both IE8 and IE9) which specifies that the browser should fall into compatibility mode when browsing sites on the local intranet. The reason for this setting existing is to allow companies who have internal sites designed for older versions of IE to upgrade to a new version without breaking those sites. It's intended to make like easier for corporate types who would rather not spend money fixing something when the broken version is good enough.
But it's a pain in the rear for the rest of us.
Obviously, if your site is on the public internet, it won't be affected by this flag, except when you're trying to work on it from localhost on your own PC. Therefore, the solution for you is to simply turn off this config setting in the browser and forget about it.
Of course, the fact remains that users of IE7 will still have this problem with your site, as their browser doesn't support the feature you're using. You could just drop support for IE7, and tell those users to upgrade. But if you want to support IE7 users, I believe that Dean Edwards' IE7.js script allows the browser to emulate this feature (along with a bunch of other stuff that Microsoft forgot).
Hope that helps.
I received this error, "DOMParser is undefined", on IE9 and it turned out to be an add-on that was disabled.
Name XML DOM Document
Publisher Microsoft Corporation
Status Enabled
Tools – Manage Add-ons – Microsoft Corporation