On Jul 4, 2006, at 3:21 PM, Giulio Cesare Solaroli wrote:
> I am working on a widget library based on MochiKit. My library has
> been inspired by the ui4web work of Leonardo Soto, but I am
> experimenting with a different "philosophy" (some of the discussion of
> this issue are available on the u
Hi Bob,
after posting the message I have given Drosera a try, but the only
"visible" result, is that it takes much longer to reach the error
condition, but no more information are available other than the
Drosera windows load the MochiKit packed file that I am using.
Is it some how possible to l
You definitely could if you recompiled Firefox, but the best way to
track this down is to just use alerts or logging until you find it.
-bob
On Jul 4, 2006, at 4:36 PM, Giulio Cesare Solaroli wrote:
> Hi Bob,
>
> after posting the message I have given Drosera a try, but the only
> "visible" r
On 4-Jul-06, at 4:44 PM, Bob Ippolito wrote:
> You definitely could if you recompiled Firefox, but the best way to
> track this down is to just use alerts or logging until you find it.
In this situation, I agree with Bob and think alert/log is your best
bet. That said, try Firefox's about:conf
Hi Bob,
I was hoping that some obscure parameter in the "about:config" page
could do the trick.
Anyway, I will try do dig this with logging.
Thanks.
Giulio Cesare
On 7/5/06, Bob Ippolito <[EMAIL PROTECTED]> wrote:
> You definitely could if you recompiled Firefox, but the best way to
> track
Hi Beau,
thank for your suggestion, but I have already changed that parameter,
but for other reason. The scope of that parameter is to avoid any
script to block the whole browser (due to excessive resource usage,
and thus extended execution time); my current problem instead is in
stack depth, and
