Why is selectivizr.js causing “white screen of death” in IE8?

后端 未结 5 643
囚心锁ツ
囚心锁ツ 2021-02-08 09:52

Including selectivizr.js is causing IE8 to not display/render anything at all, but IE8 in IETester manages.

It also downloads everything, I can see that in the activity

相关标签:
5条回答
  • 2021-02-08 10:17

    I also have the same problem with IE8, using the latest versions of jQuery and Selectivzr: I did a reverse Enginering eliminating everything else, I've seen is that the problem derives from the font-face rule.

    0 讨论(0)
  • 2021-02-08 10:19

    If this issue is related to the font-face problem with selectivizr I have created a pull request to fix this issue in our situation, basically it ignores the urls that don't contain '.css'. This fixed our WSOD issue. Its available here:

    https://github.com/JohnCashBB/selectivizr

    0 讨论(0)
  • 2021-02-08 10:21

    It sure looks to me as if you've got code on the page referencing "jQuery" before the jQuery library is actually loaded. Your sample page gets an "Object expected" error from the first line of code that references the library (right in your "about" page).

    The code appears to be setting up a "click" handler for a submit button.

    Other than that, however, the preview page renders in IE8 and there's no "white screen of death."

    edit — works fine (other than the "Object expected" error, and the related "submit" button of course) in IE7 too.

    0 讨论(0)
  • 2021-02-08 10:31

    The latest version of selectivizr (1.0.2) fixes this issue (look for WSOD): https://github.com/keithclark/selectivizr/blob/master/changelog.txt .

    EDIT: I was still having the issue even after updating to 1.0.2. There's something going on between @font-face and selectivizr, even though it doesn't occur all the time. See http://groups.google.com/group/ie-css3/browse_thread/thread/dcc21706fc009af8?pli=1 .

    0 讨论(0)
  • 2021-02-08 10:37

    Not a solution per se, but as a workaround, moving the @font-face declaration into the <head> (ie not putting it in a <link>ed stylesheet) seems to resolve this issue in many cases. Seems to be something to do with how selectivizr parses stylesheets with @font-face declarations in them.

    Not ideal I know but given that further selectivizr development seems to have stalled (last commit on GH is 1 yr ago as of time of writing) it might be acceptable in some cases.

    0 讨论(0)
提交回复
热议问题