On Aug 20, 7:38 am, Albe <[email protected]> wrote:
> Same thing here.
>
> Also, "step into" doesn't work correctly.
This statement is incorrect. Perhaps you mean: "Also 'step into' does
not work for my code".
Then I answer:
If you open bug reports with test cases I will fix them.
http://code.google.com/p/fbug/issues/list
>
> All in all i'd say that the 1.4 breed has disappointed me so far...
> nicer, some new cool things, but the old debugging has become unstable
This has not been the experience for most users. Overall I would say
that JS debugging in 1.4 is better than any previous version. There
are relatively few open bugs on debugger.
> and unreliable. Plus, when opening scripts of thousands of lines, the
> browser simply crashes.
There are no reports about such a crash. Please open URL
"about:crashes" and post the URL for the time of the crash.
>
> FYI i'm trying to debug scripts that are using Mootools+Clientcide as
> framework.
>
> I'll try to step back to 1.3 on FF 3.0...
Just to point out the obvious: since your code is somehow unusual,
bugs in Firebug related to your code won't be fixed unless you create
a test case so we can look into them.
jjb.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
