I've installed simplecart on a wordpress site
http://www.pixelligentdev.com/products/
It works fine on firefox - chrome - but not in IE11 on win8 / win10 and I can't find the issue because with debugger tool open it doesn't crash !
If you try to buy a product clicking on "order" button you'll see
It was fixed!
To track it back to source I’ve run IE with VS (Visual Studio) attached + public symbols.
The issue is a IE11 bug related to the storage events and localstorage usage. The bug was not happening when DEV tools was enabled because opening the console will set the mode to “Edge”.
Unfortunately the Microsoft’s reply is:
“This issue appears to have been fixed in Microsoft Edge. We're not presently working on feature bugs in Internet Explorer outside of security-related issues.”
The workaround is simple.
You can force IE11 to load the backwards compatibility mode to IE10.
The MS new browser (Edge) is not following that directive and IE <=10 are also ignoring it.
This can be done by adding a X-UA-Compatible meta,but this approach is not
recommended.
Instead I’ve pushed it via the header (.htaccess) to avoid page validation errors.
Changes in .htaccess
• I’ve Added to header “X-UA-Compatible” mode that will force IE11 to render as IE10.( backwards compatibility)
Header set X-UA-Compatible "IE=EmulateIE10"
Related
So I recently bought a theme that uses less css, I tested it on my local wamp server and everything worked fine in ie chrome and chrome mobile.
I then proceeded to upload it to my online server and everything worked fine in chrome, ie and then when I tested it on chrome mobile it didn't load the css, but if I use opera mobile on the same phone it loads fine, so clearly the fault is with the server but not sure what the problem could be,
Any suggestions, ?
Check your .htaccess file on your web server to check if there is any kind of caching enabled,
If there is you need to remove these data stores / caches so that the browser downloads the new content rather than rendering the cached (old) version of the CSS.
To do this on chrome select Chrome and the Clear Browsing Data
p.s. Its worth trying this even if you .htaccess draws a null just to be sure...
I've created a website using ASP.NET (C#) Framework 4.0
When running on my local IIS (in debug/release - before and after deployed) - the website is displayed correctly - as intended (checked on Internet Explorer 9, 10, Chrome and FireFox)
After I've deployed the website to my server (Windows Server 2008 DataCenter - Amazon hosting) - and only in IE 10 - the website is NOT displayed correctly - spacing is sometimes wrong, background colors sometimes disappeared, links not working properly, padding/margin is missing in some of the places and more... - it seems like the styles/CSS are partial... On other browsers (Chrome/FireFox/IE9) - it is displayed correctly (as intended)
I've tried to add the compatibility meta tags to IE=9 - didn't work (by the way, in IE10 - if I open the F12 tool - and change the Browser Mode to IE9 - it works!, but if I just change the Document Mode - it doesn't seem to help)
Why is Internet Explorer 10 evil??? Has anyone encountered this issue? any suggestions?
Thanks a lot! :)
As you write you are using F12 tools. My experience is that with Developer Tools running IE10 often does not apply all CSS rules (especially in at the end of external files). Refreshing the page or closing F12 tools usualy solves the problem. Also if you know which style is not applied it helps to disable and enable it again.
i have passe through a similar situation and some things just don't stay they way i want in every browser, so perhaps the better way out is to create CSS hacks tos specific spacing or styling issues you may have encoutered.
http://www.impressivewebs.com/ie10-css-hacks/
After a lot of searching and frustration, I've found the solution to my problem (here: http://www.nuget.org/packages/App_BrowsersUpdate)
Apparently the website should be updated to allow IE10 compatibility...
In your solution - install the ASP.NET Browser Capabilities Update using the following command in the "Package Manager Console" (can be started from "Tools"->"Library Package Manager" in your VS):
Install-Package App_BrowsersUpdate
(this will add ".browser" files to your website and few lines in your "web.config" file)
Rebuild and re-deploy your website and that's it! now my deployed website looks as intended on IE10!
(I still don't understand why it worked correctly on my localhost and not on the web server but at least the problem is solved)
Just started a site, using standard html/css - nothing fancy. Just divs to create a framed look. The server code is asp.net (4.0).
When I debug the program locally out of visual studio 2012, the page looks exactly as I designed it in all of my browsers (ie8/ff/chrome). When I publish it to my dev server and open it in IE8, the layout is messed up (i.e, my login box is now at bottom of page instead of center). However, if I open that same page on the dev server with firefox or chrome, it looks correct.
I've tried deleting all the files and republishing. I've viewed the source behind both the working (localhost) and broken (dev server) and it is identical.
Any ideas or additional troubleshooting steps I can try?
Thanks.
Edit:
Screenshot: http://i.imgur.com/tNiIFCz.png (side by side of dev vs localhost)
Masterpage: http://pastebin.com/c94Pinih
Css: http://pastebin.com/Txtac3kw
Login page: (the page that is messed up in IE8): http://pastebin.com/BN5bBamP
You could try:
make sure all of your resources are being loaded correctly (IE8 can do this, but other tools are available)
validating HTML/CSS
checking your render modes locally vs in production. If this is the issue, you can probably use the X-UA-Compatible meta tag to force a specific version of the IE render engine.
checking for any page/script errors
checking that the source in production matches the source when viewed locally
checking differences between IIS
Also by "standard html/css", I assume this is HTML4/CSS2? Do you have a link to check out?
Removed the top level div and it worked. Still not sure why it worked in ie8 on the local box, but not the dev box.
I developed an application locally using the Visual Studio 2008 built-in web server and it is running nice and neat on every single browser.
When we deployed it on the IIS6 and open it on IE8, there are rendering issues. The fonts are bigger than the other browsers (which are still nice and neat) and some components just moved around. The generated HTML is the same as the others.
How can this be fixed?
Which DOCType are you using - are you in "quirks mode" or "standards mode"?
Are you using a CSS reset?
Are you using the IE7 compatibility tag?
There are ways to fix what's "wrong" but without seeing your code, determining what's wrong is difficult.
Press F-12 in IE8 and see what browser mode you are in. If you're in "quirks mode" you're in trouble.
Thanks to Diodeus and thirtydot we figured out how to solve the problem.
The meta tag "X-UA-Compatible" allow you to control the way Internet Explorer interprets and displays your webpage. when i set , it overrides the ie7 rendering mode that IIS 6.0 puts IE 8.0 into.
Here is some useful information about that:
http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx
when I launched my site within Internet Explorer 9 I began receiving script error messages. I read the support for Internet Explorer and found out that because some sites are designed for older browsers there'll be compatibility issues until the sites are updated for Internet Explorer 9.
I found that I could add this code :
void Application_BeginRequest()
{
Response.AppendHeader("X-UA-Compatible", "IE=EmulateIE8");
}
to the Global.asax file to deal with the issue. The errors I received were from IE9.
EDIT: The errors were fixed but I want to know if there is an alternative method to making a website compatible with IE9? Also what are the differences between the way IE8 interprets Javascript code and IE9?
What you did is correct. This is one of the server side way to handle this. Alternately, you can set this in HTML header (will be painful as you have to do it for all the pages)
On a related note - read the IE compatibility blog which has more details on this topic:
http://blogs.msdn.com/b/ie/archive/2010/06/16/ie-s-compatibility-features-for-site-developers.aspx