I built a web app using some technologies that do not work well for IE 8/9. The app functions well in Chrome and Firefox and mostly okay in Standard IE 10 but breaks down in IE 8/9 standard. However, if I switch over to quirks mode for IE 8/9 in the developer console, it works perfectly for some reason. Is there a danger to trying to force quirks mode for older IE?
Well I would say that it's definitely not optimal and you should be trying to fix the errors that prevents you to run in standard mode, however if you are unable to do it and it's the only way to go, I do not see how a working application running in quirks mode could be worse than a failing application in standard mode.
Related
I am using Prime faces form and the exe was being launched on button click through Javascript using ActiveX Object.This functionality was working fine in IE(Internet Explorer) but Edge is not supporting ActiveX Object.
Anybody know the alternate of it?
Earlier We have tried with ActiveXObject and was working fine.
Except VGR's solution, I think there's no programmatical way to open exe file in a modern browser. But if you're using Edge, you can open that page in IE mode. Edge IE mode supports ActiveX controls.
Edge IE mode is designed for organizations that still need IE 11 for backward compatibility with existing websites but also need a modern browser. If you're in an organization, you can configure IE mode policies to make that page always open in IE mode. Or you can just use Edge settings to configure IE mode pages.
I have written a bootstrap page and it works just perfectly on all browsers i have tested....except ie11 with enterprise mode on.
It seems to stretch everything to full width as if my screen is a giant phone. Im sure other things are broken in it but thats the first thing you see.
Anybody have any ideas if Bootstrap and Enterprise mode dont play well? I see some posts asking the question and some responses saying to force ie9 10 or edge mode but that wont work with enterprise mode as it overrides that...ie think.
From MSDN:
Enterprise Mode, a compatibility mode that runs on Internet Explorer 11 on Windows 8.1 Update and Windows 7 devices, lets websites render using a modified browser configuration that’s designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
And from Bootstrap:
On Windows, we support Internet Explorer 8-11
So if you are running Enterprise mode in IE7 mode, Bootstrap will do all sorts of odd things. The solution would be to run in IE8 mode which may fix a lot of issues or don't add this site to the list.
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 get reports that a button does not work in my webapp on IE8 (and older). Everything works in IE9, FF and Chrome. The error is triggered in this click-bind:
$("#save_refresh").click(function(e) {
alert('hello world!');
});
This is the html:
<input class='button' type='button' value='Save / Refresh' id='save_refresh' />
When clicking the button in IETester running IE8, the "hello world!" is not shown and I get this error:
Line: 17
Character: 28691
Error:
Code: 0
URL: jquery-1.6.1.min.js
So my question is:
is there anything wrong with my above code OR does anyone know how to debug javascript in older version of IE.
I agree with Quentin. You should download one of Microsoft's Internet Explorer Application Compatibility VPC Images to properly test your code. Paul Irish has a good article on the incompatibilities of Internet Explorer compatibility modes.
The IE9 compatibility modes are unreliable in terms of giving you an accurate picture of how the browser will actually render your page and how your page will behave under that browser. It's like putting a Chevrolet Metro engine in your Chevrolet Aveo so you can test drive the Metro.
That said, when using IE8, you can just hit F12 like in IE9, but with IE7, you need to have a copy of Visual Studio and use the debugger keyword.
Microsoft provide virtual machines with older versions of Internet Explorer for testing.
Using IE9, you can switch to the IE7 or IE8 rendering engine. Press F12 and the developer panel should appear. The header bar has options to switch to the IE7 and IE8 Browser Modes (and their respective notorious Quirks Modes).
For IE6, you'll have to rely on Virtual Machines (as mentioned by Quentin above). Microsoft released XP Mode partly for this.
Internet explorer has compatibility mode for IE7 and IE8 (and even for Quirks mode), it which you can debug most of the issues. Rarely you need true installation of older version 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