John, all my attempts at producing a test case have failed, but I did
find a workaround that may provide a clue, or maybe point this issue
in a different direction.
In our app, firebug (and venkman!) with both freeze the UI in ff3 if
the breakpoint or error occurs somewhere within our window's load
event handler (we're actually using Prototype's Event.observe for
this, but that doesn't seem to matter). Here's the strange part: if I
wrap the contents of that event hander in a setTimeout( function()
{...}, 1 ), debugging works just fine.
On Sep 20, 9:37 am, John J Barton <[EMAIL PROTECTED]> wrote:
> Since so many people have had success, you must have something set
> into your environment which is odd. One approach that I have found
> helpful is to load Firebug in to a new Firefox
> profile:http://kb.mozillazine.org/Profile_Manager
>
> Also are you running in en-US Firefox or a localized version? We have
> been struggling to improve our internationalization, but its not as
> solid as en-US as yet.
>
> jjb
>
> On Sep 20, 3:18 am, Francois Piat <[EMAIL PROTECTED]> wrote:
>
> > > There are no bug reports on breakpoints. I'd fix them if you produce
> > > a test case where I can see the problem.
>
> > Sorry, I cannot produce a test case. I had too many problems (little,
> > but the sum is consequent) and I have downgrade to previous version (:-
> > (((
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
