install firebug 1.5x 0a05 inspect element is now working better like
the shortcut key.... the bugs are still there though.

"I really don't think word 'suck' can be used in
the same sentence with 'firebug'. "

when I say suck it shouldn't taken as insulting an entire product
often it is only ever small areas within the product that suck.. and
could be improved :)

And firebug is good, but its not perfect. IE8 web developer tools and
Google chrome have introduced certain areas that are better than
Firebug now.. overall Firebug is still better with addons etc, but
using something that's not just the best at everything is lame.











On Jun 20, 10:17 pm, yoni <[email protected]> wrote:
> hello.
> i am now using the latest release candidate and latest firebug
> ffirebug-1.4X.0b2 and i still cannot get ctrl+shift+c to work if i
> haven't already pressed F12 to get firebug up there. i loved the old
> firebug; where i could be browsing and ctrl+shift+c brought up
> firebug.. what should i do?
> thanks!
>
> On Jun 20, 6:24 am, Alexander Podgorny <[email protected]>
> wrote:
>
> > Just off the topic, I really don't think word 'suck' can be used in
> > the same sentence with 'firebug'.
> > It is free, it is great and it is getting better.
> > Thanks firebuggers for the wonderful product that saved all of us so
> > much headache.
>
> > On Jun 17, 2:43 pm, Xeonz <[email protected]> wrote:
>
> > > I've just gone and amended the rev3246  to Fb1.5x 0a03 release... and
> > > yes at least the inspect element tool is doing something now.. but its
> > > pretty much working in a sucky way.
>
> > > you invoke the inspect element tool and already half your browser
> > > screen space is gone because the fbug! window pop ups (into default
> > > position! it doesn't remember).. you should be able to use the inspect
> > > element toolbar icon/shortcut freely with full window space.. until
> > > you select an element and only then fbug opens up.
>
> > > if we can get that put back to how it used to work would be much
> > > better.
>
> > >  my next bug.. using the inspect element tool once the fbug window is
> > > opened.. if you leave an element selection highlighted with the blue/
> > > yelllow shading(any future options of customization for fbug like
> > > selection colors? like through an actual extensions Options dialog?)
> > > over its element.. and then close the fbug window.. it does not clear
> > > the selection.. you'll be left with a fbug element selection
> > > highlighting still visible on the page. Even though fbug has been
> > > closed and you're no longer using the inspect element tool.. there
> > > should be some sort of thing that clears element selections when you
> > > close fbug which it is not doing.. so a user has to make sure they
> > > have messed about to remove any element selections off before closing
> > > the fbug window..  would be nice to see this fixed please.
--~--~---------~--~----~------------~-------~--~----~
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