Test case/Repro:

1. In Firefox open any webpage on the internet.
2. Activate firebug
3. Activate the element selector (the blueish arrow)
4. Select any element on a page.
5. You should now be looking at the split pane HTML tab content with HTML content on the left, highlighting the HTML element you've selected and on the right.
6. Click on any of the CSS Filenames on the right hand side of the CSS preview (this will take you to the CSS Document tab view)
7. Make an arbitrary addition or edit to the CSS document
8. Re-activate the element selector
9. Click on any element on the page
10. The CSS panel fails to appear in HTML view this time around, and other times it appears but is dark grey with the "Style, Computed, Layout, DOM" headings that react on mouse hover but will not react to click.

Was working fine until I updated to latest firebug this evening.

After performing some more tests i've found that the CSS panel inconsistently opens, though consistently is unusable.

Repro this by following the above steps, then simply clicking between the HTML and Script Firebug tabs. Clicking DOM, then HTML shows no CSS Pane. Script, then HTML shows dark-grey CSS Pane. It seems like weird behavior, perhaps I've not had enough sleep :)

Hope this helps :)

Firebug version (number): 1.10.0a9 Browser version: FireFox 12 Operating system: Win7 32bit Pro SP1

Upgraded Firefox->Aurora 14.0a2, Firebug working perfectly again! :)

I have the same problem with the right panel.

Grayed right panel bug: 1. display html panel 2. click on "computed" or any other tab ==> right panel is grayed 3. close and reopen FB ==> right panel is back

No right panel 1. display html panel 2. click on "console" or any other tab ==> right panel disappears 3. close and reopen FB ==> right panel is back

It was working fine with FB 1.10.0a8. The bug is on any website.

Firebug version (number): 1.10.0a9 (new profile with only Firebug) Browser version: FireFox 12 Operating system: Win7 32bit Ultimate SP1

This should be fixed in https://github.com/firebug/firebug/commit/1ea0715d121a9c2ea026bfe21f78d9dd05cbed48.

Added a fallback functionality in case the new APIs for pseudo-class locking aren't available. See the related issue 3230 for more info.

Thanks for the feedback!

Sebastian

Issue 5501 has been merged into this issue.

Issue 5510 has been merged into this issue.

Issue 5511 has been merged into this issue.

Issue 5517 has been merged into this issue.

Just change the summary of this issue to be more clear about what's the problem.

Sebastian

This issue (one of 18) has been fixed in Firebug 1.10a10 http://getfirebug.com/releases/firebug/1.10/firebug-1.10.0a10.xpi

Please check it out and let us know if the fix works for you.

Thanks for the help! Honza

I've been camped on the release directory waiting for this one. I had been having the same problem as the OP and it occurred during a period where I was trying to debug CSS entries. Just downloaded and tried a10 and the Style and Layout panels are again working for me. Many thanks for the fix.

Dave

Thanks for the verification!

Sebastian

Hello I just updated to a10 hoping it would resolve this issue, but I still have this problem. The right-side pane of the CSS editing "disappears" furthermore firefile consistently tells me that "firebug" is not started and thus can't save CSS file edits (might be unrelated to this issue though).

My steps to reproduce are:

1. Open firebug, see the CSS right-side bar just fine
2. Click on a different tab with another website on it.
3. Click back on the first tab, the CSS sidebar is gone. (fail point)
4. To get it back, close firebug, then open it again, side bar is "back"

Have to do this many times every day to keep it "working"

I have tried with a fresh profile and no other extensions/add-ons installed, issue still occurs.

Problem was present on OSX Snow L. and now still present in Mountain Lion as well.

Latest production-release of Firefox.

Thanks for any help you can offer!

Sounds like you are talking about a bug in FireFile and not Firebug. If that's so, please create a new issue there:

https://github.com/tobiasstrebitzer/FireFile/issues

It's definitely unrelated to the issue described here. Furthermore note that the current stable release of Firebug is 1.10.3, not alpha 10.

Sebastian