elm-lang.org shows a blank page on IE8 and IE9 about compiler HOT 8 CLOSED

Yeah, I have noticed this issue recently. For me, whenever I open the developer console, the site suddenly starts working again. As in, any effort to debug the code removes the conditions that caused the error. I am pretty sure it is a cross-browser compatibility issue within versions of IE (and weirdly IE does not default to the standards compliant version).

I believe that my last finding here was that IE8 did not support the JSON object or something like that. At that point I decided to wait for a bug report before throwing time into the IE black hole. So thanks for the report; I'll take a look tonight and see what I can find!

from compiler.

I gave this some more thought. I think the root cause is how I am importing modules in JS. We shall see!

from compiler.

I believe IE9 should be working now. The "bug" was totally ridiculous. I had written in some module var raise = console.log; and in IE9 (a "modern" browser) this was a bug! The console object only exists in IE9 if you open the developer console, so it is undefined when you run the page and defined when you try to debug it! ARGGGG!

Anyway, IE9 and IE10 appear to be working. I think the overlap between IE8 users and Elm users is too low at this point to devote a huge amount of time and energy to it. Especially considering that Elm needs a decent number of HTML5 features.

from compiler.

Also, can you verify that IE9 is working?

from compiler.

I was actually posting this issue on behalf of a colleague ... he is in the process of creating a github account so might be aswering this himself.

I agree that IE8 is a target that can be ignored -- our use case (page on a embedded webserver of a industrial device) probably has some want be users who want to use old IE's but its ok if we support any IE. Much easier to tell them to upgrade their browser (which would be a good idea to do regularly anyway) than tell them to make their IT department install a different type of browser.

Yay for fixing this!

from compiler.

No problem! I wish your colleague the best, and he should never hesitate to reach out to me if he runs into an issue. A great way to choose what features to add is to hear issues from current users :)

I can push an incremental release of the compiler that fixes this issue in the next couple days. I'll add a comment here when I do :) This release will basically just get rid of that one line in Elm's JS code.

from compiler.

Yeah, IE9 now works fine! Your examples as well as the homepage.
I'm the colleague of peerst - thanks a lot for fixing it!

Right, the IE8 ist not much important, anyway I had a look on it - maybe you can fix it with very little effort - I got the error message (without debugging):
"Your browser may not be supported. Are you using a modern browser?
Runtime Error in Main module:
Module 'Website.Skeleton' is missing. Compile with --make flag or load missing module in a separate JavaScript file.
The problem may stem from an improper usage of:
skeleton, tile, toTile"

Then run again and debugger enabled:
"Breaking on JScript runtime error ..."
"Object doesn't support this property or method -- elm-mini.js, line 123 character 357"

from compiler.

No problem, I had been meaning to fix it soon! I am happy to hear you are considering using Elm for your project :)

The errors you are seeing are deceptively simple. The error messages are optimized to make it easier for users to debug code they write, but the error messages are pretty useless for debugging errors within the Elm runtime system (RTS). Fortunately, I am the only person who has to deal with the RTS, and I know the code well enough that it is not really an issue. In any case, I think it would be quite a bit of work to get IE8 working, and even then it would only be a partial implementation.

from compiler.