Just in case anyone is crawling SO for an answer to this, the above two answers aren’t solving the core problem which is answered here – CSS media query not working in IE 9 Basically inline CSS3 media queries DO work in IE9 but you have to disable Compatibilty mode – <meta http-equiv=”X-UA-Compatible” content=”IE=9″> The … Read more
I would use Modernizr to detect when css animations are not supported. With Modernizr, it’s as simple as: if(!Modernizr.cssanimations) { //jQuery fallback } As for rotating with jQuery I would use: http://jqueryrotate.com/
Maybe you like to check the links below: Making cross domain JavaScript requests using XMLHttpRequest or XDomainRequest XMLHttpRequest – Mozilla Developer Network A good summary of the jQuery x-domain requests Which browser supports x-domain?
I have exactly the same problem as well. you may want to read this https://connect.microsoft.com/IE/feedback/details/649949/innerhtml-formatting-issues-on-very-large-tables YOu can remove the space inbetween td by using javascript if your html is returned from ajax, then from the response, you replace it with response_html = response_html.replace(/td>\s+<td/g,’td><td’); $(‘#table’).html(response_html);
I can only explain you how to fix the “CSS3114” error. You have to change the embedding level of your TTF file. Using the appropriate tool you can set it to installable embedding allowed. For a 64-bit version, check @user22600’s answer.
You could use: document.getElementById(‘iframe1′).contentWindow.document.write(“<html><body>Hello world</body></html>”); Here’s a jsFiddle, which works in all major browsers. Note that instead of contentDocument.write you should use contentWindow.document.write: this makes it work in IE7 as well.
To get more consistent scaling across browsers always ensure you specify a viewBox but leave off the width and height attributes on your svg element. I’ve created a test page for comparing the effect of specifying the different SVG attributes in combination with widths and heights specified in CSS. Compare it side by side in … Read more
Actually the user agent string is different for IE9 when being run in IE7 compatibility mode, so this would be one of the best ways to distinguish between different IE versions. Introducing IE9’s User Agent String: Similar to IE8, IE9’s Compatibility View will map to IE7 Standards Mode, and IE9’s UA string when in Compatibility … Read more
Placing: <meta http-equiv=”X-UA-Compatible” content=”IE=edge,chrome=1″> in the <head> tag should do it.
Many JavaScript libraries (especially non-recent ones) do not handle IE9 well because it breaks with IE8 in the handling of a lot of things. JS code that sniffs for IE will fail quite frequently in IE9, unless such code is rewritten to handle IE9 specifically. Before the JS code is updated, you should use the … Read more