Been combing the code and searching google/stack/forums for a while, but no luck. I've got a layout built with bootstrap 3 that uses should be 4 columns at lg, 3 at md, 2 at sm and 1 at sm. It works on all browsers except ie8. On ie8, only one column is shown as the col-xs-12 is overriding everything. I have implemented the require.js script, the IE=Edge meta tag, and think I have the scripts loading in the correct order. Below is the html/css/js. Anyone catch anything that I didn't?
https://gist.github.com/anonymous/6978014
There was a bug in the require.js script somewhere. Pulled down the latest minified version and it suddenly worked. :P
Related
DNN 09.09.01 / 2sxc 11. 22.1 / Image Gallery v5
App installation without problem, but when you click on image to show in Fancy box - you got message; The requested content can not be loaded. Please try again later.
I tested this with 2sic DNN Instant Bootstrap 4 theme and it is working just fine.
However, on this site I am using other DNN Theme ("Professional" Theme from DNNVista, Bootstrap 3, link; https://store.dnnsoftware.com/home/product-details/professional-15-colors-mega-menu-bootstrap-responsive-dnn-6x-7x-8x-dnn-9x) and this error occurred every time I click on a single photo.
I am aware that this Theme is full of bugs and I probably wasted 99$ for it, but would like to find out what is wrong and try to fix it in this particular Theme.
But - I don't know where to start, because there is no errors in Admin Log.
Any similar situations or ideas, please?
(sorry if I did not express my self clearly - English is not my Mother Tongue. Please ask if you need clarification)
UPDATE:
I found that, from some reason, hyperlinks for pictures are parsed without question mark after filename, but can't find a reason for such behaviour because everything is correct in app template.
Just a guess - probably you have some JS replacing other JS - like Fancybox being loaded 2x in different versions. Best check the Chrome-Network to verify.
I am creating a Wordpress theme with Bootstrap 3.
I add html5shiv.js and respond.min.js in head and, now, the theme works in IE8.
When I open the website, for a second and only in IE8, the layout isn't correct and then is perfect.
What is the best practice to fix this initial visualisation problem?
Stop using Ie8, it is dead ....
I solve with a css "respond-fix.css" inside conditional comment with this css code:
body{visibility:hidden} #media screen and (min-width:1px){body{visibility:visible}}
We have a chart that is rendering incorrectly in IE8. We just updated the Highcharts.js file yesterday with the latest version as we were receiving a script error on "d.join". Now we don't get any script error and our page continues to load properly, a step in the right direction, however the chart is missing the axis and plot lines and the coloring.
Here is what the chart looks like in Chrome/IE10/IE9:
and in IE 8:
Please help me figure this out. Thanks!
It looks like your problem is due to upgrading to jQuery 2.x. jQuery has intentionally dropped support for Internet Explorer 8 and below. See http://blog.jquery.com/2013/04/18/jquery-2-0-released/
Your solution would be to either
Downgrade to jQuery 1.x
Drop your support for Internet Explorer 8
I just completed a site: http://www.justcelebrations.co.in . I haven't launched it yet because of certain problems. The site uses css3 text gradients to style text in span and border radius to style most divs. It has to be made dynamic later so I don't want to change the text effects to images or something. The problem I am facing is that the site hangs IE8. I haven't tested it in lower versions of IE. I have tested the markup thoroughly and its validated and the css too is valid except for features which are from css3 like opacity, border-radius etc. I have also added google script to make ie behave properly and mordenizer library. The site still hangs IE8. Please Help me out here..
EDIT: after a lot of testing and debugging, found out that ie<9 were crashing because of some text elements being styled by p:first-letter or h1:first-letter (which, as is the case with ie, is totally random as :first-letter is supported by IE7+ ). So all i did was separated those styles from base.css to a non-ie.css and loaded that file with a [if ! lt IE 9]
and it worked!
after a lot of testing and debugging, found out that ie<9 were crashing because of some text elements being styled by p:first-letter or h1:first-letter (which, as is the case with ie, is totally random as :first-letter is supported by IE7+ ). So all i did was separated those styles from base.css to a non-ie.css and loaded that file with a [if ! lt IE 9] and it worked!
Can you add <!--[if IE 8 ]><html class="ie ie8" lang="en"> <![endif]--> to target fixes. As you make changes view in IE8 through IE9(F12) and play with -ie-(compared to -moz- & -o-) in your css. I would also keep a CSS 2.1 file and a CSS3 file to keep track of your new code.
It's working good here in Safari. Just to narrow this down, what if you remove all the conditional and IE specific libraries you got from Google? In my experience, all the various JS libraries that are supposed to make older IE versions behave always seem to break or conflict with some other script or library like jQuery.
Also see the answer in this thread for optimizing your page loading by placing the JavaScripts at the end of the <body> section. Perhaps in your case, loading the JS last will make some kind of difference to Explorer.
I have a problem concerning dojox.charting, after updating to the new version of dojo IE 8 doesn't show the labels of my charts anymore. Seems to be a dojox.gfx text problem.
See with IE8:
http://download.dojotoolkit.org/release-1.4.0/dojo-release-1.4.0/dojox/gfx/tests/test_text.html
Any idea how to fix that?
Cheers
-jstr
It looks like some IE8 fix pushed by MS broke it because we didn't modify this code for a long time.
In any case there is a ticket for this problem (reported as a charting ticket): http://bugs.dojotoolkit.org/ticket/10491
One simple fix for now is to force IE7 mode:
<meta http-equiv=“X-UA-Compatible” content=“IE=7” />
More info can be found in Understanding Compatibility Modes in Internet Explorer 8.