On Feb 18, 2008 4:58 AM, Ralf Nieuwenhuijsen
<[EMAIL PROTECTED]> wrote:
> I was wondering about this... i've been hit by it as well. But only
> when using firebug.
> This fixes it for me. It seems more general though!
>
> It also happens with errors that take place as the result of a timer
> event.
I was wondering about this... i've been hit by it as well. But only
when using firebug.
This fixes it for me. It seems more general though!
It also happens with errors that take place as the result of a timer
event. Perhaps all async type of request have this behavior with
firebug.
2008/2/14, Gae
On Thu, Feb 14, 2008 at 3:02 PM, Gaetan de Menten <[EMAIL PROTECTED]> wrote:
>
> On Wed, Feb 13, 2008 at 9:53 AM, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
> > >
> > > I've been having the following problem for quite a while: whenever I
> > > throw an exception in a code which is executed in a
On Wed, Feb 13, 2008 at 9:53 AM, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
> >
> > I've been having the following problem for quite a while: whenever I
> > throw an exception in a code which is executed in a callback of a
> > request, nothing noticeable happens, except the request just timeouts
Hi Gaetan,
> Hi list,
>
> I've been having the following problem for quite a while: whenever I
> throw an exception in a code which is executed in a callback of a
> request, nothing noticeable happens, except the request just timeouts
> (ie the initial exception is not printed in the (Firebug) con
On Feb 12, 2008 1:20 PM, Andreas Junghans <[EMAIL PROTECTED]> wrote:
> OK, I just tried it with firebug, and I still don't see it. And it
> would make absolutely no sense! Could you send the snippet you used
> for testing? Or, if your code is part of a complex application, try
> to reproduce it wit
Hi Derrell,
Am 12.02.2008 um 19:07 schrieb Derrell Lipman:
> On Feb 12, 2008 12:46 PM, Andreas Junghans <[EMAIL PROTECTED]
> ida.de> wrote:
>>> I discovered another related problem recently. throw new Error()
>>> doesn't actually process the thrown error until after completion of
>>> the curren
On Feb 12, 2008 12:46 PM, Andreas Junghans <[EMAIL PROTECTED]> wrote:
> > I discovered another related problem recently. throw new Error()
> > doesn't actually process the thrown error until after completion of
> > the current javascript context. For example, if you have a loop and
> > an error i
On Feb 12, 2008 6:46 PM, Andreas Junghans <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Am 12.02.2008 um 18:07 schrieb Derrell Lipman:
>
> > On Feb 12, 2008 11:59 AM, Gaetan de Menten <[EMAIL PROTECTED]>
> > wrote:
> >> Hi list,
> >>
> >> I've been having the following problem for quite a while: whenever I
Hi,
Am 12.02.2008 um 18:07 schrieb Derrell Lipman:
> On Feb 12, 2008 11:59 AM, Gaetan de Menten <[EMAIL PROTECTED]>
> wrote:
>> Hi list,
>>
>> I've been having the following problem for quite a while: whenever I
>> throw an exception in a code which is executed in a callback of a
>> request, no
On Feb 12, 2008 11:59 AM, Gaetan de Menten <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> I've been having the following problem for quite a while: whenever I
> throw an exception in a code which is executed in a callback of a
> request, nothing noticeable happens, except the request just timeouts
> ...
Hi list,
I've been having the following problem for quite a while: whenever I
throw an exception in a code which is executed in a callback of a
request, nothing noticeable happens, except the request just timeouts
(ie the initial exception is not printed in the (Firebug) console).
var req = new q
12 matches
Mail list logo
