Empty page in IE8 about css3-mediaqueries-js HOT 13 OPEN

same here, IE8 just crushes and I have to shut it down as a process, also used 
browsershots.org to test the site, same there on IE8 screenshots, so their test 
browser crushes too, tried it on another computer and another opsys, same there 
too.
this lib doesn't work under IE8 :(

The library works in IE8. However, the page content is hidden and then re-shown 
after half a second delay.

On some sites when marginLeft of the document is set to a big negative number 
to hide the content until media queries are applied, the screen goes blank for 
a split second, before the marginLeft is reset.

For some reason that doesn't happen on all sites.

Please, suggest a solutions that can be used without breaking core 
functionality of the library.

Hi, i'm having the same issue, and i notice the margin left. But still the 
script is breaking on IE8 and IE7. Any solution to this issue??

I am having this same issue. I found that I can make it work again if I remove 
some of my styles inside of media queries. Can't pinpoint what's causing this

The reason for the bug is, that the IE8 and below can only have 32 Stylesheets 
or inline style tags. Since the css3-mediaquers.js adds every mediaquery as a 
single style tag, it will reach the 32 pretty fast.

I get my web designer to write another css special for IE 8 responsive design 
fixes. No intention to give it perfect. 
IE10 in with Windows 8 now. Ahh.. IE just headache!!!!!!!!

I'm also experiencing this issue. Forcing IE to avoid Compatability Mode seems 
to have helped on some user's browsers who were having this problem, but the 
Error on line 408, related to styles being called persists on all instances of 
IE8 I've tried. I was not aware of the 32 stylesheet maximum in IE8 and if it 
parses the way you describe, that makes sense to me. I'll try removing @media 
styles to see if this makes a difference on the site. Thanks.

I found if I replaced my local version of css3-mediaqueries.js with the hosted 
code.google version, it resolved the line 408 error and also displayed the page 
properly. It did, however, give a minor (no dialogue box pop up) error in line 
3 of the Google code. However, that seems to have allowed it to render the page 
just fine. I'm moving on with that solution, but wish there were one that 
generated no errors in IE8.

I had the same error with the max amount of style elements in IE8 (@#8).
Changed the script to append all styles in one style element with id attribute. 


addStyle: function (s, process) {
var el;
if (null !== document.getElementById('css-mediaqueries-js')) {
  el = document.getElementById('css-mediaqueries-js');
}
else {
  el = document.createElement('style');
  el.setAttribute('type', 'text/css');
  el.setAttribute('id', 'css-mediaqueries-js');
  document.getElementsByTagName('head')[0].appendChild(el);
}
if (el.styleSheet) { // IE
  el.styleSheet.cssText += s;
}
[...]



removeStyle: function (el) {
  if (el.parentNode)
    return el.parentNode.removeChild(el);
}

FOR ME THE PROBLEM WAS A FACEBOOK PLUGIN .WHENE I DID DISABLE THE FZCEBOOK 
PLUGIN AND TWITTER AND GOOGLE PLUS ALL WORKED FINE 

THE FACEBOOK PLUGING MAKE UPDATES SO HE CHANGE IN THE TIME ,THEN YOU CAN T BE 
SURE TO BE COMPATIBLE WITH THIS SCRIPT, I ADVICE TO DISABLE IT OR MAKE JUST A 
LINK TO IT IN OTHER PAGE, DON T INTEGRATE FACEBOOK BOX FOR EXEMPLE JUST MAKE A 
LINK TO IT IN OTHER PAGE OR DISABLE IT , ME PERSONALLY I DON T LIKE IT BECAUSE 
IT DESTROY THE DSIGN OF MY SITE AND COLORS. AND AS I SAYS FACEBOOK CHANGE IN 
TIME THEN THIS UPDATES CAN MAKE PROBLEMS WITH OTHER SCRIPTS LIKE JQUERY OR 
OTHERS.

TO KNOW WITCH SCRIPT IS MAKING THE PROBLEM IN IE8 JUST CLICK TOOLS IN IE8 THEN 
CLICK DEVELOPPER TOOLS THEN CLICK SCRIPT THERE YOU WILL HAVE A CONSOL TELLING 
YOU THE ERRORS AND WITCH SCRIPT IS AFFECTING

SORRY MY ENGLISH I DON T HAVE TIME TO CORRECT IT :(  
GOOD LUCK :)

To #10 Sebastian:

Fixed blankpage issue for us,

Thanks a Million!

Back from the dead... There is a new version of the script. It has some CSS 
parsing and processing improvements. If you're still using it, or would like to 
try again, could you confirm that this issue is solved or not?