Johan Sundström wrote: > On 5/4/07, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> I have a JSON file that works in Firefox but when the Exhibit >> presentation I use it with is viewed in Internet Explorer (both 7 and 6) >> an Object Error is given and nothing is displayed. I have validated the >> file with Babel and it is syntactically correct. Do you have any advice >> and or any knowledge of this issue presenting its self? >> > > The always asked return question: do you have or can you craft some > page on a url you could share with us for debugging the issue? (The > rest of the comment might quite likely not be at all relevant to you.) > > If you're using the 2.0 api, I've had reports from users about IE7 (at > least) bailing out reporting something like that (for > application/jsonp based exhibits of mine, at least). > > To David: the use of catch()ing errors and routing them to alert() > breaks debugability of the _actual_ error not only for Firefox, but IE > as well. I've tried setting up an IE with a debugger (see > http://www.berniecode.com/blog/2007/03/08/how-to-debug-javascript-with-visual-web-developer-express/ > for a tutorial on how to do that, by the way), but ended up with the > same problem there. > > It's possible that rethrowing them after the alert (perhaps only on > detecting an url parameter errors=throw) might make it more > debuggable; I haven't experimented much yet. I'd somehow want to find > a solution to this though, as I presently just glaze over when IE has > issues. Most of my hacking at the core parts is for fun, and debugging > IE with hands tied fails that threshold with a margin. Good idea about errors=throw. Do you think that will get IE's debugger to the original exception location or to the location of rethrow?
David _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
