On Aug 2, 10:46 am, goodtest <[email protected]> wrote:
> I have tried using new profile, but it didn't help much. Also, going
> by bug count doesnt really help. How many *major* issues and *major*
> annoyances would help.
Zero, or we would not release. Well major annoyances may not: we did
not understand one aspect of Firebug use until way late in the 1.4
cycle. We rarely or never used the red [X] in upper right corner so we
didn't realize that was how some users minimize.
>
> Anyway, here are the specific issues:
> 1. If one of the object is null or undefined, it won't complain - BIG
> issue. It only complain if we have "stop on all errors" turned ON.
Huh?
> 2. If we have "stop on all errors" turned ON, it shows the error right-
> on-the-javascript-code. Its very hard to read whats wrong.
I guess you mean "break on errors". Yes, I got stuck on that, I can't
figure out how to make the error message background opaque. So if the
message is long and the source is long and your screen is narrow, you
can't read it. Note that is not true for everyone in every case.
> 3. Every now and then "New Watch Expression" stops working. i.e.
> throws some NSException. I usually see this after I keep firebug
> stopped at a debug-point for 5 minutes or so and then try to evaluate
> some javascript expression.
which exception?
(NH answered the rest).
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
-~----------~----~----~----~------~----~------~--~---
