I personally don't like how firebug operates now regarding site
specific operation.  The way I use it seems to be mostly typical going
by this thread.  I want it open for all of the sites I visit during
the day (sites that my company develops for), but I never want it open
for any google app.  If I leave firebug on and go to my companies
email google app my browser eventually hangs and hogs up 50% of my
cpu.  Regarding having multiple profiles open, this seems like I would
be working around a bug when in fact I am trying to circumvent a new
design direction.

On Jun 30, 11:35 pm, johnjbarton <[email protected]> wrote:
> On Jun 30, 7:49 pm, MorningZ <[email protected]> wrote:
>
> > "But this IS the common use case: We have a site of our own that we're
> > debugging. We want Firebug up all the time for that site and never for
> > others."
>
> > EXACTLY!!!
>
> Ok, so open firebug on that site. Next time you return to that site
> Firebug will be open.
>
> Unless you can me help understand why this does not work for you I
> can't help.
>
>
>
> > I totally fail to understand how that behavior is a "bug" that needed
> > to be fixed.....
>
> > I thought after i made my last post: "screw it, i'll just 'turn on for
> > all websites' and deal with it this way"....
>
> > then 10 mins later as i checked my email i was rudely reminded just
> > how much Gmail + Firebug = extreme failure
>
> What kind of failure are you referring to?  I know that Gmail +
> Firefox 2.0 + Firebug 1.2 is a problem. But that was, well, years
> ago.  Even with Firebug active I don't think its such a big deal.
>
>
>
> > "We have been working and previewing this design for many months"
>
> > And i bet the # of people using this preview is just a drop in the
> > bucket compared to the people using whatever version is 
> > athttp://www.getfirebug.com(whichas i type this, is 1.3.3)....
>
> Yes, and the number of people who have complained is a drop in the
> bucket compared to the number of beta users (about 8,000). What do we
> conclude? Not much I am afraid to say.
>
> While I am naturally defensive about our work on 1.4, I do value the
> comments from people who speak up. For example, the comments by users
> about 1.3 motivated the changes you see in 1.4. So beware! ;-)
>
>
>
> > I mean come on now, there's lots of topics in this mailing list of
> > people who don't like this "bug fix", surely there's enough feedback
> > to at least think about making the change...
>
> Lots of thought and time when in to 1.4. Honestly we did not make this
> change lightly.
>
> Lots of folks did not like 1.3 either. Now everyone who posts says 1.3
> is great. So what are we to think?
>
> I will tell you a secret: the way to make a convincing argument for
> change is to describe in detail what happens in your use. Detailed and
> specific. That way we can tell if your experience is a bug, a problem
> in communications, or real problem with the design.
>
>
>
> > I saw someone post on another topic this page:
>
> >http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-...
>
> > There's two comments there, and they echo what we are all echoing
> > here:  1.4's activation model is counter intuitive ** and not day to
> > day developer friendly **...  but if your focus has shifted from being
> > the absolute must have JavaScript developer tool (believe me, it was,
> > as it actually roped me into FireFox as my everyday browser) to a
> > plugin my father could use (good god), then whatever, i guess it's "3)
> > We can't satisfied everybody"
>
> Our focus it to make Firebug effective for all users. To the best of
> my knowledge there is only one use case that 1.4 really does badly,
> sites that generate unique URLs.
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to