On Sep 10, 12:17 pm, Nicolas Hatier <[email protected]> wrote:
> The problem is not consistent enough to create a test case - I attempted
> to create one, but the bug does not trigger everytime.
>
> When is a24 due?
Your release is ready for you now ;-)
jjb
>
> Nicolas
>
> johnjbarton wrote:
>
> > On Sep 10, 10:37 am, roeya <[email protected]> wrote:
>
> >> I have the same problem with 1.4.2 and FF 3.0.1.3 it drives me crazy
> >> it
>
> > But the important question is does it drive you to create a test case
> > so we can fix it?
>
> > jjb
>
> >> Roeya
>
> >> On Sep 10, 6:20 pm, johnjbarton <[email protected]> wrote:
>
> >>> If it is a23, I probably fixed it yesterday. Perhaps a24 later today
> >>> will help.
> >>> jjb
>
> >>> On Sep 9, 10:50 pm, Nicolas Hatier <[email protected]> wrote:
>
> >>>> Hello.
>
> >>>> Since a few versions (1.5X.0a22, 23 maybe), I have problems with
> >>>> breakpoints. Sometimes they trigger, sometimes they don't. Sometimes
> >>>> they get disabled. I can't find a consistent behavior, nor a
> >>>> reproducible pattern.
>
> >>>> I use jQuery in the thing I'm currently trying to debug, and all
> >>>> breakpoints are displayed as "undefined" (but with correct file and
> >>>> line#) in the breakpoints tab.
>
> >>>> Any idea, or something I could do to diagnose or fix this?
>
> >>>> Firefox 3.5.3
>
> >>>> NH
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
