IE Errors on this Page?

Is anyone else getting a “Stack Overflow” error message when they access this page with Internet Explorer?

17 Responses to “IE Errors on this Page?”

  1. Fred Chamberlain Says:

    I’m all good here, as far as Iknow. I’m not particularly computer savvy, but I can reply and don’t see any error messages jumping out at my on the main blog page.

    BTW, a piece of original artwork that I purchased on ebay last week arrived today in the mail. If anyone has any interest in it, feel free to e-mail me and I’ll send you a pic. A nice piece from the Arkham Asylum mini-series. 😉


  2. badMike Says:

    Yes, I’m getting that in IE. It says “Stack overflow error at line: 1487.” For kicks, I decided to take a look at the code, which doesn’t even go up to line 1487 (it only goes up to about line 1150 or so). I’ve never seen that error before so I don’t know what it means. And your blog doesn’t look like it could have overflow anything.

  3. Alex Krislov Says:

    I get the message occasionally, but not today. Ergo, if you ask about it, it fixes the error.

  4. Beth Says:

    Not today. But a while back…

  5. berk Says:

    Yeah, I get it every time I look at the blog.

  6. François Says:

    Yes, every time I visit your blog.

  7. Steve Gerber Says:

    Thanks for the responses. I’m trying to track down the cause.

    My apologies for the annoyance.

  8. Forrest Says:

    (pause to save page and reboot into Windows)

    IE6 gives a warning about unsafe objects but that’s all.

    Then again I was viewing offline, which means things like the .css files didn’t get hauled in, so that’s something to consider (along with that duplicate “head” tag).

  9. Micah Says:

    Internet Explorer is crap and I no longer use it. I use Safari or Mozilla (which I think is the same as Firefox).

    I find that I get fewer fuck ups like that, pages look like they are supposed to, and other media within a page will work properly more often.

    Oh, and I have never had an error message or any problem loading your page.

  10. Brian Spence Says:

    I use Firefox, and now I can’t see the left hand side of your page.

  11. Brian Spence Says:

    Um, that was stupid. I meant that I can’t see the RIGHT hand side of your page (the ads and links).

  12. Charles Bryan Says:

    I usually use Opera, but I tried the site with IE, and everything came through fine.

  13. A.L. Baroza Says:

    Never had a problem with Firefox.

  14. Steve Gerber Says:

    I’ve been fiddling with the site all afternoon. At one point, I intentionally disabled the sidebar on the right, which is why Brian couldn’t see it during that logon. (It’s back now.)

    The problem is associated only with Internet Explorer. It doesn’t show up in Firefox and probably wouldn’t in Opera, either.

    Anyway, I think I may have found the glitch. Those of you who’ve seen the error message before, let me know if it’s gone.

    Re the browser debate:

    We can rail against IE till half-past Ragnarok, but lots of people still use it (including myself, in a way; see below), and my job here is to make the blog accessible to all. I can’t insist that people use a different browser just to log onto this site.

    FWIW, I use a front end for IE called Maxthon that I happen to like very much. It adds tabbed browsing and does a couple of tricks — e.g., opening multiple tabs automatically on startup — that I haven’t been able to duplicate with Firefox. Nonetheless, I completely understand why users are fleeing IE and anything vaguely related to it *en masse*. Firefox is a terrific program.

  15. Alex Krislov Says:

    I’m not getting the error message anymore. Looks like your poking about turned the trick.

    I still use IE, myself, simply because it’s the most common browser. To keep Netscape’s Books Community and Politics Forum running, I need to see what most of our subscribers are seeing. Personally, I prefer Firefox–but I rarely use it.

  16. berk Says:

    Yup. The error message is no more. I’m impressed!

  17. Roger Green Says:

    I did for many months, not today.