My timeline works beautifully in all browsers except IE 6.0 on PC, where i
get Caught exception: [ Object Error ]
URL of timeline:
http://www.forbes.com/static_html/2007/achievement/achieve_o_meter.html
[Submitted by nina on simile.mit.edu]
David F. Huynh - 03/Mar/07 10:50 AM
Nina, it's most probably an XML encoding issue. Try this a dichotomy method
to locate the offending part of your XML:
- Remove the later half of your XML file. If it works, then the problem is
in the later half. Otherwise, the problem is in the first half.
- For the half that is problematic, remove its later half, ...
[ Show » ]
David F. Huynh - 03/Mar/07 10:50 AM Nina, it's most probably an XML
encoding issue. Try this a dichotomy method to locate the offending part of
your XML: - Remove the later half of your XML file. If it works, then the
problem is in the later half. Otherwise, the problem is in the first half.
- For the half that is problematic, remove its later half, ...
[ Permlink | « Hide ]
nicolaus bauman - 04/Aug/08 05:53 PM
My timeline allows viewing scores of thousands of events. Chunks of events
are lazily loaded via a scroll listener as static JSON-encoded files that
are generated offline as a batch (to prevent overwhelming the database) as
the user scrolls into the past. Everything works fine in Firefox, Safari
and Opera. But I have inconsistent results in IE6 and IE7. Most of the
time, some chunk is causing a "Exception caught [Object error]". It's
pretty random, but some files seem more consistent than others, with the
occasional "runtime error" or whatnot. I have played with the content
numerous times, but my results are inconsistent. I have also checked the
content with the Babel validator: it says my content is fine. It seems that
the problem is not anything to do with encoding, but has something to do
with a threading issue or a reentrance problem or some kind of race
condition either in Timeline or in IE itself.
Original issue reported on code.google.com by GabrielR...@googlemail.com on 6 Apr 2009 at 2:00
Original issue reported on code.google.com by
GabrielR...@googlemail.comon 6 Apr 2009 at 2:00