On Aug 21, 8:48 am, Michael <[email protected]> wrote:
> I must use Firebug for development.
Excellent. Welcome.
>
> If you have Firebug "off for all pages", then expand firebug, then
> refresh the page, firebug goes away, and turns off. You then cannot
> see the initial ajax of the page until you turn Firebug on again. This
> is unacceptable. You can't see if one of the scripts/css/images are
> giving you 404's, etc, etc.
Good news: I have a simple fix for you: Don't use "Off for Alll
Pages". Because if you use off for all pages you will get exactly the
results you describe, because that is what the option supposed to do.
If you don't want Firebug to turn off on all pages, well then don't
set "Off for All Pages".
>
> If you have Firebug "on for all pages", then Firefox becomes
> completely unusable. With 3 tabs open (especially iGoogle) the entire
> browser grinds to a hault.
More good news! Another simple fix! Don't use "On for all Pages".
Patient: 'Hey Doc, I see green flashy stuff when I press on my
eyeball".
Doc: "Don't press on your eyeball".
> Unfortunately because Firebug is critical to the development of a web
> application, I must use Firebug. This means that I now use Google
> Chrome for "non web development." AKA: My entire development team has
> moved to Chrome for normal browsing activity, while CTRL+ALT+DELing
> Firefox occasionally during development.
I'm not sure what you are saying here. Here is what I heard:
Firebug is essential to our work.
I have an issue with Firebug.
Instead of reporting a test case we are browsing the web with a
second browser.
How would I best reply to this?
>
> I know the religious Firebug repliers in this forum say "no change
> from previous version" "works as intended" "just enable for all and
The "On For All Web pages" and "Off For All Web Pages" were not in
previous versions. Based on your description above they are working as
intended. I do not recall ever saying 'just enable for all and then
blacklist single pages'. In fact this is specifically not supported in
1.4.
> then blacklist single pages." Understand that while I might be the
> minority on this forum, millions of people abandon Firebug without
Millions? Look, you have a problem. All you have to do is explain the
problem. You really don't have to make up a story about how important
the problem is. If you take the trouble to report the problem clearly
and work with us until we can reproduce it, then we will fix it.
(BTW the closest we have to data on adoption shows about 2.3M Firebug
users with no significant drop off:
https://addons.mozilla.org/en-US/statistics/addon/1843)
> complaining. The change is a real impact to the usability of the
> plugin.
What change?
>
> I have a quad core 3GHz computer with 2TB of high performance raid
> with 8 Gigs of ram in Windows Vista 64.
I'm sure this is relevant to your problem. I just can't see how.
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
-~----------~----~----~----~------~----~------~--~---
