When is eval not an option due to memory leaks and bugs..? And in what
browsers?
True, eval is powerful, and the slowest function in JS, but I've only been
able to find one bug with it, a major one, and that was in Netscape 4.
(I'd explain it, because it's sooo freaky, and it has to do with protot
Hi Bart,
> When is eval not an option due to memory leaks and bugs..? And in what
> browsers?
We aren't talking about small functions which are executed by eval,
but about large amounts of code. I can't give you specific references
other than the suggestion to search for eval in groups.google.co
An Image widget does make sense, but there are some problems with DynImage. There are
some bugs with it, and some the preloading code isn't really needed (keeping a list of
image src's etc).
DynImage is a better option that writing the string in a DynLayer because you
have extra Image specif
Quite a few of you have written me and informed me that on slower machines
DynAPI Ultra edition is rather slow to decompress. I've also just taken a
look at DOMapi and am quite impressed. Its not as broad as DynAPI in terms
of compatibility with 4+ browsers but it is smaller. However, domAPI lacks
