kriszyp/xstyle

Issues with xstyle and Win10 CTP IE 11

kelko opened this issue · 2 comments

kelko commented

The Internet Explorer 11 in the current Win10 CTP has a problem with xstyle which causes sites of ours to not work in that new IE.

The method "checkParser(styleSheetElement)" in css.js has the following code part

var parser = testElementStyle('x-parse', null, 'content');
if(parser && parser != 'none'){
    require([eval(parser)], function(parser){ ... }
}

The problem here is, that with the new IE the testElementStyle call does return neither null nor 'none' but 'normal', which does not fit the if check but of course can't be eval-ed and thus the JavaScript engine throws an error:

SCRIPT5009: 'normal' is undefined
onekopaka commented

Changing the following line:

if(parser && parser != 'none'){

to:

if(parser && parser != 'none' && parser != 'normal'){

appears to have fixed things.

  • 👍2
paulirish commented

This issue cropped up again as Chrome changed its behavior. It just hit stable in Chrome 51 this week.

Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=609848

  • 👍3