Inspect Element -Broken???

[Xeonz]

Whats happened the toolbar icon 'Inspect Element' doesn't work anymore

and neither does the shortcut ctrl+shift+c

it seems the only way to get it back is to f12 and use it from there
when firebug has opened.

also another highly annoying issue is that even if you add the firebug
toolbar icon to the toolbar.. it doesn't open firebug inside the frame
like f12 does.. no instead it opens in a new window.. really
annoying.. how can't I change this?

using ff3.5b4 firebug versions latest 1.4 and 1.5 no worky

[johnjbarton]

We were not successful with FF 3.5b4 either. You can try the 3.5
nightly build:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/
If that fails, the next thing to try is a new Firefox profile, see
http://groups.google.com/group/firebug/web/faq-about-firebug

jjb

[Xeonz]

nope its broken new profile..same version..

and also in that newer build FF build.. with newest firebug..

Boken!.. really sucks without the inspect element shortcut!!

On Jun 6, 3:24 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> We were not successful with FF 3.5b4 either.  You can try the 3.5

> nightly build:http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla...
> If that fails, the next thing to try is a new Firefox profile, seehttp://groups.google.com/group/firebug/web/faq-about-firebug

[johnjbarton]

If you really must use FF 3.5, please use the version recommended
here:
http://blog.getfirebug.com/?p=200
The older and newer versions don't work well.

jjb

[Nicholas Orr]

FF 3.0.10

FB 1.4.0a31

If i have the firebug console open in a window and then right click a element on the page and choose "inspect element", the firebug window closes. I right the element on the page again, firebug opens at the bottom of the browser window, then I pop it out into a new window do what I want. if I right click a different element and click "inspect element" the firebug window closes again.

This is on a fresh install on FireFox (i just reinstalled windows last night)

Nick

[johnjbarton]

Fixed for 1.5a4 and 1.4b3. (R3210 on branches/firebug1.5)
jjb


On Jun 11, 4:25 pm, Nicholas Orr <nicholas....@zxgen.net> wrote:
> FF 3.0.10FB 1.4.0a31

>
> If i have the firebug console open in a window and then right click a
> element on the page and choose "inspect element", the firebug window closes.
> I right the element on the page again, firebug opens at the bottom of the
> browser window, then I pop it out into a new window do what I want. if I
> right click a different element and click "inspect element" the firebug
> window closes again.
>
> This is on a fresh install on FireFox (i just reinstalled windows last
> night)
>
> Nick
>

[yoni]

Hello I'm using fresh install, new profile of firefox 3.5b4 and
firebug 1.4.0b1; ctrl+shift+c does not work to inspect element. do you
know why that may be?

[johnjbarton]

Please try the version of FF 3.5 describe here:
http://blog.getfirebug.com/?p=200

Please try firebug 1.4b2 from http://getfirebug.com/releases/1.4X

If you still have a problem and you are using Firebug in the browser
(not in a separate window), then let us know.

jjb

[Xeonz]

http://blog.getfirebug.com/?p=200 that ff build and FB 1.4b2 tested..
still broken

did you even try it yourself jjb?

well I must have tried every new version under the sun..
newer Firefox builds and Firebug are NOT allowing the Inspect Element/
ctrl-shift-c function/shortcut to work..

[johnjbarton]

One of the reasons that the issues list works better than newsgroups
is that we can stay focused on a single issue. I've fixed one issue
discussed here and I have tested inspect on the version of Firefox 3.5
from June 5.

You have tried a new profile and the Jun 5 version. So something else
is wrong. Either I'm not reproducing the steps you use, the distro
version is not the same as the one we use, or your environment is
somehow different from mine.

Here is what I do to test it:
Install June 5 FF 3.5 from the blog post cited previously.
Using Firebug 1.5a3
Open http://www.mozilla.org/projects/shiretoko/
Put my mouse for the planet image and right click, select Inspect
Element.
Firebug opens on the HTML panel and selects an img tag with src ending
"...deerpark-icon.png"

Does this fail for you?

jjb

On Jun 16, 7:37 am, Xeonz <ikoo...@gmail.com> wrote:
> http://blog.getfirebug.com/?p=200that ff build and FB 1.4b2 tested..

[Andrew]

My inspect element broke as well, but I may have a different problem
than all of you. I'm running:

Firefox 3.0.11
Firebug 1.3.3
OSX 10.5.7

Everything was working fine until this morning, and now the inspect
element is broken. I can't select anything by clicking on it, but I
can find and highlight it through the DOM. The inspect button appears
to be always selected.

Andrew

On Jun 16, 8:37 am, Xeonz <ikoo...@gmail.com> wrote:
> http://blog.getfirebug.com/?p=200that ff build and FB 1.4b2 tested..

[Xeonz]

jjb..

inspect element as in the toolbar icon(pair of glasses) or using ctrl
+shift+c.... is not the same as using the context menu on an element
and then selecting inspect element.

the functionality missing is the interactive element highlighting
before the Fbug window frame is opened.. something you also get with
Fbug open (f12) and using the same inspect element tool.

"Here is what I do to test it:
Install June 5 FF 3.5 from the blog post cited previously.
Using Firebug 1.5a3
Open http://www.mozilla.org/projects/shiretoko/
Put my mouse for the planet image and right click, select Inspect
Element.
Firebug opens on the HTML panel and selects an img tag with src ending
"...deerpark-icon.png"

Does this fail for you? "

This doesn't fail for me on my main FF3.5b99 FB1.5x(currently) .. but
it was never the same thing as what my reported issue was about
either.

What my issue is about is still an issue as its something that has
worked in earlier versions and not anymore.

On Jun 16, 6:58 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> One of the reasons that the issues list works better than newsgroups
> is that we can stay focused on a single issue. I've fixed one issue
> discussed here and I have tested inspect on the version of Firefox 3.5
> from June 5.
>
> You have tried a new profile and the Jun 5 version. So something else
> is wrong.  Either I'm not reproducing the steps you use, the distro
> version is not the same as the one we use, or your environment is
> somehow different from mine.
>
> Here is what I do to test it:
>  Install June 5 FF 3.5 from the blog post cited previously.
>  Using Firebug 1.5a3

>  Openhttp://www.mozilla.org/projects/shiretoko/

>  Put my mouse for the planet image and right click, select Inspect
> Element.
> Firebug opens on the HTML panel and selects an img tag with src ending
> "...deerpark-icon.png"
>
> Does this fail for you?
>
> jjb
>
> On Jun 16, 7:37 am, Xeonz <ikoo...@gmail.com> wrote:
>

> >http://blog.getfirebug.com/?p=200thatff build and FB 1.4b2 tested..

[johnjbarton]

Ok good we are making progress. We now know that what I am doing works
for both of us. Now the only remaining problem is to figure out what
it is that fails for you.

See below...

On Jun 16, 1:49 pm, Xeonz <ikoo...@gmail.com> wrote:
> jjb..
>
> inspect element as in the toolbar icon(pair of glasses) or using ctrl
> +shift+c.... is not the same as using the context menu on an element
> and then selecting inspect element.

What pair of glasses?

Here is how I test ctrl+shift=C:

Install June 5 FF 3.5 from the blog post cited previously.
Using Firebug 1.5a3
Open http://www.mozilla.org/projects/shiretoko/

Open Firebug.
Put my mouse for the planet image and push cntrl+shift+C

Firebug opens on the HTML panel and selects an img tag with src
ending "...deerpark-icon.png"

>

> the functionality missing is the interactive element highlighting
> before the Fbug window frame is opened.. something you also get with
> Fbug open (f12) and using the same inspect element tool.

I don't understand what you mean here.

jjb

[Xeonz]

"What pair of glasses? "

"Inspect".. the toolbar icon is in the customize toolbar dialog....
using it will give you the interactive element highlighting...same as
using the searchlight icon in Fbug

On Jun 16, 10:15 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> Ok good we are making progress. We now know that what I am doing works
> for both of us. Now the only remaining problem is to figure out what
> it is that fails for you.
>
> See below...
>
> On Jun 16, 1:49 pm, Xeonz <ikoo...@gmail.com> wrote:
>
> > jjb..
>
> > inspect element as in the toolbar icon(pair of glasses) or using ctrl
> > +shift+c.... is not the same as using the context menu on an element
> > and then selecting inspect element.
>
> What pair of glasses?
>
> Here is how I test ctrl+shift=C:
> Install June 5 FF 3.5 from the blog post cited previously.
>  Using Firebug 1.5a3

> Openhttp://www.mozilla.org/projects/shiretoko/

[johnjbarton]

Please tell me the text on the buttons or menus you are using. I don't
think Firebug has a customize toolbar dialog.

jjb

[Mike Ratcliffe]

I never saw the pair of glasses before ... right-click the Firefox
toolbar and select customize. You can drag the glasses icon to the
Firefox toolbar and then click done.

This creates an inspect shortcut in the Firefox toolbar.

Clicking on this icon when Firebug is disabled does nothing. I suppose
we should either:
1. Disable this icon when Firebug is not active
2. Activate Firebug and begin inspecting when it is clicked.

I think option 2 would be better. I won't have time to look at this
tonight but I will in the next few days.

-
Mike Ratcliffe

[johnjbarton]

Ah, ok, you have to right click on the area at the top of the browser
where "File Edit View" etc menus are shown.

There is also option #3: remove this feature we did not know even
existed.

But I just tested it and it works. I think I fixed it yesterday at
R3246 when I allowed cntrl+shift+c to be defined even when Firebug is
not active.

And sure enough there is an eyeglasses icon: chrome://firebug/skin/inspect.png.
It would be nice to sync these with the rest of the UI.

jjb

On Jun 17, 2:31 am, Mike Ratcliffe <mich...@ratcliffefamily.org>
wrote:

[Xeonz]

there is much fail going on in this thread I can't believe I've only
just got to the point where my first post is understood.

how can you guys not even know about a feature that already exists in
firebug

"There is also option #3: remove this feature we did not know even
existed. "

jeesh :( this would be incredibly stupid imo

"But I just tested it and it works. I think I fixed it yesterday at
R3246 when I allowed cntrl+shift+c to be defined even when Firebug is
not active"

well this is how it worked before.. and makes sense!.. a similar setup
can be had with the dom inspecter addon...for use on browser.xul.. and
I use that aswel.

I mean how silly is it to go through extra steps to make sure firebug
is already running before the inspect element can be invoked.. it was
never like this before!.. And ideally the first thing I do is go
straight for the inspect element toolbar icon..its just quicker (how
earth you guys didn't even know about that :S ) I find the
interactive element highlighting quite useful to use,and only once
I've selected an element will firebug open up in the window
frame..with the selection... just get things back to how they used to
be please.

anyway has this rev3246 updated been included in any of the fb1.4 or
1.5 releases? currently on ff3.5rc b2 and using fb1.4x.0b2 still not
working.. "firebug-1.5X.0a03.xpi 08-Jun-2009" ..probably not worth
testing.

[Xeonz]

"Activate Firebug and begin inspecting when it is clicked"

no this would suck! especially if by activate firebug you mean load
its its windowframe!. .. and so would option 1.. both your suggestions
suck.

get it to how it was before.. just because I use the inspect element
tool.. doesn't always mean I want the firebug window opening up! ...
reason being is that inspect element highlitinig is quick way of
seeing the layout of site elements.



On Jun 17, 10:31 am, Mike Ratcliffe <mich...@ratcliffefamily.org>
wrote:

[Xeonz]

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.

[johnjbarton]

On Jun 17, 10:16 am, Xeonz <ikoo...@gmail.com> wrote:
> there is much fail going on in this thread I can't believe I've only
> just got to the point where my first post is understood.

I think if you post such problems to the issues list we can focus on
getting the steps needed to reproduce the problem. In addition you
are using FF 3.5 which was still in beta and had lots of problems. In
retrospect I wished I had suggested you use FF3.0.

>
> how can you guys not even know about a feature that already exists in
> firebug

Because we did not write all of the code. I did not even know about
toolbarpallette until yesterday.

>
> "There is also option #3: remove this feature we did not know even
> existed. "
>
> jeesh :( this would be incredibly stupid imo

But you are the first user in two years to mention this feature. We
have to make hard choices sometimes, and one criteria is "how many
users will the change affect". I don't think very many people use
toolbar customization any more. Nevertheless it looks easy to support
this feature.

>
> "But I just tested it and it works. I think I fixed it yesterday at
> R3246 when I allowed cntrl+shift+c to be defined even when Firebug is
> not active"
>
> well this is how it worked before.. and makes sense!.. a similar setup
> can be had with the dom inspecter addon...for use on browser.xul.. and
> I use that aswel.

Other users complained about the impact of having Firebug active, it
is now inactive by default. Since it was inactive, the key combo did
not work; since the key combo did not work, the toolbar customization
did not work. That's how bugs happen. Its not like we tried to break
it.

>
>  I mean how silly is it to go through extra steps to make sure firebug
> is already running before the inspect element can be invoked..  it was
> never like this before!.. And ideally the first thing I do is go
> straight for the inspect element toolbar icon..its just quicker (how
> earth you guys didn't even know about that :S )  I find the

Its even faster to use context menu Inspect or just the key combo
cntrl-shift-C

> interactive element highlighting quite useful to use,and only once
> I've selected an element will firebug open up in the window
> frame..with the selection... just get things back to how they used to
> be please.
>
> anyway has this rev3246 updated been included in any of the fb1.4 or
> 1.5 releases? currently on ff3.5rc b2 and using fb1.4x.0b2 still not
> working.. "firebug-1.5X.0a03.xpi   08-Jun-2009" ..probably not worth
> testing.

The fix will be in Firebug 1.5a4. I hope it can be today but I don't
know yet.

jjb

[Xeonz]

[Mike Ratcliffe]

If you find any bugs then please add them to our issues list:
http://code.google.com/p/fbug/issues/list

[Alexander Podgorny]

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.

[yoni]

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 <alexander.podgo...@gmail.com>
wrote:

[Hernan Rodriguez Colmeiro]

This is a known bug, and at least there is one bug report about it:
http://code.google.com/p/fbug/issues/detail?id=1892

Hernán

[madriss]

Hello,

I'm experiencing the same issue with Firefox 3.5 RC2 and Firebug
1.4.0b2. The "Inspect Element" icon on the toolbar does nothing, nor
does Ctrl + Shift + C. However, both work if Firebug is already open.
In Firefox 3.0.x, both methods opened Firebug and started the "Inspect
Element" function, whether Firebug was already open or not.

A fix would be much appreciated. Thanks :-)

[johnjbarton]

Please try Firebug 1.5a5 from http://getfirebug.com/releases/firebug/1.5X.
The problem should be fixed.
jjb

[Xeonz]

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 <yonat...@gmail.com> wrote:

[johnjbarton]

On Jun 21, 10:07 am, Xeonz <ikoo...@gmail.com> wrote:
> install firebug 1.5x 0a05 inspect element is now working better like
> the shortcut key.... the bugs are still there though.
>

Our bug reporting system is at
http://code.google.com/p/fbug/issues/list

jjb

[Xeonz]

http://code.google.com/p/fbug/issues/detail?id=1885


Also another bug is in the Style tab when hiding an element like
"display: block" instantly causes the style tab css listings to become
corrupted and an imminent browser crash.

tbh I dunno why there can't be a quicker way of resetting the css
settings either, and also making it easier for web developers to make
changes to css code and get some sort export on all the code changes
they've made.. so any css elements they've disabled/changed +any new
ones they've added.. or maybe a way of committing changes to the css
file if a local source link is provided... definitely many areas fbug
could be improved on.

[yoni]

the problem is indeed fixed!! thanks jjb.

however, there still remains a difference that i think was integral.
say i was browsing, pressed CtrlShiftC to highlight an element. i saw
that element, etc, and wanted to continue browsing, i could push Esc a
couple of times and Firebug would close on its own. now i have to
click F12 to close it. not a huge deal at all, but is there a reason
this was changed?

On Jun 21, 11:20 am, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> Please try Firebug 1.5a5 fromhttp://getfirebug.com/releases/firebug/1.5X.

[Xeonz]

that what I have been getting at already... you can't just use the
inspect element tool to hover over elements without having the entire
fbug bugging window coming up..

they've broken the workflow because they didn't have any idea about it
themselves it seems.

[IHSW]

Happens to me too. I'm switching to Opera 10 for Dragonfly.

This issue with Firebug is a real deal-breaker for me.

[johnjbarton]

On Jun 22, 11:59 am, yoni <yonat...@gmail.com> wrote:
> the problem is indeed fixed!! thanks jjb.
>
> however, there still remains a difference that i think was integral.
> say i was browsing, pressed CtrlShiftC to highlight an element. i saw
> that element, etc, and wanted to continue browsing, i could push Esc a
> couple of times and Firebug would close on its own. now i have to
> click F12 to close it. not a huge deal at all, but is there a reason
> this was changed?

Because we did not know it existed and perhaps we accidently broke
it? There is 35000 lines of code here, and only 45 some test cases so
far.
jjb

[johnjbarton]

On Jun 23, 10:45 am, Xeonz <ikoo...@gmail.com> wrote:
> that what I have been getting at already... you can't just use the
> inspect element tool to hover over elements without having the entire
> fbug bugging window coming up..
>
> they've broken the workflow because they didn't have any idea about it
> themselves it seems.

What workflow?
We write debuggers. So no, we don't know how everyone uses Firebug.
There are lots and lots of different ways people us Firebug. We know
how some people use Firebug because they explained it in terms of the
Firebug user interface features. If you do the same may be we can
help.

jjb

[johnjbarton]

On Jul 8, 9:22 am, IHSW <iamhiddensomewh...@gmail.com> wrote:
> Happens to me too. I'm switching to Opera 10 for Dragonfly.

Awesome, please let us know how that works out. One of our goals is to
push all the other tools and to learn from all the other tools. If you
find something there you like let us know.

>
> This issue with Firebug is a real deal-breaker for me.

I could not make sense of the other post, so referring to it as "this
issue" does not help.

jjb