Firebug CSS not working

34 views
Skip to first unread message

Kyle Hayes

unread,
May 12, 2009, 11:48:02 AM5/12/09
to Firebug
FF v.3.0.10
FB v.1.3.3

All of the sudden CSS debugging stopped working and I'm no longer able
to change properties on the fly. If I do try to change a property and
escape out of the editing, the selector disappears. There just seems
to be a lot of issues with the CSS pane all of the sudden.

I've restarted fb/ff, and I've also attempted uninstalling firebug and
reinstalling it.

Any ideas?
-Kyle

johnjbarton

unread,
May 12, 2009, 11:50:30 AM5/12/09
to Firebug
Try a new Firefox profile:
http://groups.google.com/group/firebug/web/faq-about-firebug
bet that fixes it.

jjb

Kyle Hayes

unread,
May 12, 2009, 12:09:33 PM5/12/09
to Firebug
I'm very saddened to report that this did not work. I just now tried
it and I am getting the same issue as before.

Kyle Hayes

unread,
May 12, 2009, 12:11:54 PM5/12/09
to Firebug
Here is a screencast to show what is happening:
http://screencast.com/t/omNzONF0hyz

johnjbarton

unread,
May 12, 2009, 12:43:19 PM5/12/09
to Firebug
Looks like you have two copies of the stylesheet, I've heard that
confuses Firebug.
jjb

Kyle Hayes

unread,
May 12, 2009, 1:38:00 PM5/12/09
to Firebug
Yeah, and it appears it was the server doing it for some reason. Very
strange. It works now. Thanks!

brian.tully

unread,
Jun 30, 2009, 1:31:39 PM6/30/09
to Firebug
Wow - I'm having the same exact issue based on your screencast. Very,
very, odd. Tried reinstalling Firebug to no avail. I definitely don't
have 2 copies of the same stylesheet. This just started happening
yesterday and it's really thrown a monkey wrench into my dev flow. I
am so dependent on Firebug it's not funny. I've been forced to use
Safari 4's web inspector, but I really hope there is a fix for
Firebug.

FWIW I'm using FF 3.0.11 and Firebug 1.3.3 on Mac OS X 10.5.7


On May 12, 12:11 pm, Kyle Hayes <mrkyleha...@gmail.com> wrote:
> Here is a screencast to show what is happening:http://screencast.com/t/omNzONF0hyz
>
> On May 12, 9:09 am, Kyle Hayes <mrkyleha...@gmail.com> wrote:
>
>
>
> > I'm very saddened to report that this didnotwork. I just now tried
> > it and I am getting the same issue as before.
>
> > On May 12, 8:50 am, johnjbarton <johnjbar...@johnjbarton.com> wrote:
>
> > > Try a new Firefox profile:http://groups.google.com/group/firebug/web/faq-about-firebug
> > > bet that fixes it.
>
> > > jjb
>
> > > On May 12, 8:48 am, Kyle Hayes <mrkyleha...@gmail.com> wrote:
>
> > > > FF v.3.0.10
> > > > FB v.1.3.3
>
> > > > All of the suddenCSSdebugging stoppedworkingand I'm no longer able
> > > > to change properties on the fly. If I do try to change a property and
> > > > escape out of the editing, the selector disappears. There just seems
> > > > to be a lot of issues with theCSSpane all of the sudden.

Pappy

unread,
Jun 30, 2009, 1:58:25 PM6/30/09
to Firebug
Just to add another two proof points, a co-worker and I see the exact
same issue with FF 3.5 and FB1.4.0b3.

johnjbarton

unread,
Jun 30, 2009, 2:54:09 PM6/30/09
to Firebug
We can't fix it unless you give us a procedure to reproduce it.
jjb

johnjbarton

unread,
Jun 30, 2009, 2:54:27 PM6/30/09
to Firebug
We need test cases.
jjb

On Jun 30, 10:58 am, Pappy <papp...@gmail.com> wrote:

Pappy

unread,
Jun 30, 2009, 5:07:06 PM6/30/09
to Firebug
Step-by-step:

OS X: 10.5.7
Firefox: 3.5 Release
Firebug: 1.4.0b3

- Start Firefox with a clean profile (Firefox -P)
- Browse to http://getfirebug, install Firebug, restart Firefox
- On "http://www.mozilla.com/en-US/firefox/central/", right-click on
"Some of our favorite sites", select "Inspect Element"
- Change the 'margin-top' value (eg. select it and press up-arrow).
Note margin doesn't actually seem to change.
- Click off the CSS editing area. Notice the key you were just
editing disappears, as well as the rule description for that block.

Just to be clear, this is happening for any page and any html element
for me.

johnjbarton

unread,
Jun 30, 2009, 7:47:50 PM6/30/09
to Firebug
Sounds like issue 1894
http://code.google.com/p/fbug/issues/detail?id=1894
which I fixed last week. Its no in 1.4b3.

jjb

On Jun 30, 2:07 pm, Pappy <papp...@gmail.com> wrote:
> Step-by-step:
>
> OS X: 10.5.7
> Firefox: 3.5 Release
> Firebug: 1.4.0b3
>
> - Start Firefox with a clean profile (Firefox -P)
> - Browse tohttp://getfirebug, install Firebug, restart Firefox

Liam

unread,
Jun 30, 2009, 6:48:57 PM6/30/09
to Firebug
Exactly as above on pc and mac at the company I work for when we all
upggraded to 3.5 which is final and out today.

- All addons off, different addons, new profile tried etc.
- Some elements work but others if you change a margin etc will break.
- Intermitant error on functionality, sometimes it will change, other
times it wont.

This is now a BIG problem since firefox 3.5 is out as a final release
and firebug used by a lot of developers and currently not working. You
will be getting a lot of contacts now in regard to this bug.

On Jul 1, 9:07 am, Pappy <papp...@gmail.com> wrote:
> Step-by-step:
>
> OS X: 10.5.7
> Firefox: 3.5 Release
> Firebug: 1.4.0b3
>
> - Start Firefox with a clean profile (Firefox -P)
> - Browse tohttp://getfirebug, install Firebug, restart Firefox

johnjbarton

unread,
Jun 30, 2009, 7:53:08 PM6/30/09
to Firebug


On Jun 30, 3:48 pm, Liam <ldil...@gmail.com> wrote:
> This is now a BIG problem since firefox 3.5 is out as a final release
> and firebug used by a lot of developers and currently not working. You
> will be getting a lot of contacts now in regard to this bug.

But as I've tried to point out earlier, one contact with a test case
is all we need to fix it.

jjb

Liam

unread,
Jun 30, 2009, 8:03:23 PM6/30/09
to Firebug
What sort of test case? I have seen guys link you some videos and
myself showing the problem in the RC1 of 3.5, the person above me has
also given a step by step and information.

I am also getting these errrors:
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIStreamListener.onStartRequest]" nsresult:
"0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
file:///C:/Users/Liam/AppData/Roaming/Mozilla/Firefox/Profiles/mfrai3t9.default/extensions/fir...@software.joehewitt.com/components/firebug-channel-listener.js
:: anonymous :: line 135" data: no]
Source File:
file:///C:/Users/Liam/AppData/Roaming/Mozilla/Firefox/Profiles/mfrai3t9.default/extensions/fir...@software.joehewitt.com/components/firebug-channel-listener.js
Line: 135

johnjbarton

unread,
Jun 30, 2009, 8:41:24 PM6/30/09
to Firebug


On Jun 30, 5:03 pm, Liam <ldil...@gmail.com> wrote:
> What sort of test case? I have seen guys link you some videos and
> myself showing the problem in the RC1 of 3.5, the person above me has
> also given a step by step and information.

A test case is file or set of files and a detailed step by step
instruction list to reproduce the problem on my machine. A public URL
is also fine if the site not too complicated.

Videos help but only in the case that someone is having a hard time
describing a visual problem in the user interface.

"Me too" also helps if the problem is hard to reproduce. Each user
tends to say a bit more about how it happens for them and eventually
we get clues.

>
> I am also getting these errrors:
> Error: [Exception... "Component returned failure code: 0x80004005
> (NS_ERROR_FAILURE) [nsIStreamListener.onStartRequest]"  nsresult:
> "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
> file:///C:/Users/Liam/AppData/Roaming/Mozilla/Firefox/Profiles/mfrai3t9.default/extensions/fire...@software.joehewitt.com/components/firebug-channel-listener.js
> :: anonymous :: line 135"  data: no]
> Source File:
> file:///C:/Users/Liam/AppData/Roaming/Mozilla/Firefox/Profiles/mfrai3t9.default/extensions/fire...@software.joehewitt.com/components/firebug-channel-listener.js
> Line: 135

This is fixed in 1.5a6, http://getfirebug.com/releases/firebug/15X.

jjb

Pappy

unread,
Jun 30, 2009, 10:48:05 PM6/30/09
to Firebug
Agreed. It sounds *exactly* like that. Any clues as to when we can
expect 1.4b4?

As for the 'test case' stuff. I understand requesting a step-by-step
set of instructions, but requiring a set of sample files (assuming you
are referring to the firefox/firebug binaries) is pretty heavy-
handed.

From my (and apparently others') perspectives, we provided all the
'test cases' we realistically could (or should) for this particular
problem.

Anyway, the solution seems to be wait for 1.4b4... I'm okay with that
as long as it shows up pretty quickly :)

_jason

On Jun 30, 4:47 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> Sounds like issue 1894http://code.google.com/p/fbug/issues/detail?id=1894

johnjbarton

unread,
Jun 30, 2009, 11:18:17 PM6/30/09
to Firebug


On Jun 30, 7:48 pm, Pappy <papp...@gmail.com> wrote:
> Agreed.  It sounds *exactly* like that.  Any clues as to when we can
> expect 1.4b4?

We trying to get 1.4.0 Thursday morning. But right now it's not
looking good.

>
> As for the 'test case' stuff.  I understand requesting a step-by-step
> set of instructions, but requiring a set of sample files (assuming you
> are referring to the firefox/firebug binaries) is pretty heavy-
> handed.

Test web pages. See for example, these bug reports:
http://code.google.com/p/fbug/issues/list?can=1&q=label:Test-case-available%20OR%20label:testcase

>
> From my (and apparently others') perspectives, we provided all the
> 'test cases' we realistically could (or should) for this particular
> problem.

There is one test case here from "Pappy'. I doubt the fix I created
for that problem will solve so many problems. The fix only applies in
rather unusual cases.

>
> Anyway, the solution seems to be wait for 1.4b4... I'm okay with that
> as long as it shows up pretty quickly :)

Frankly I'm doubtful. My guess is that you have another problem.

jjb

jitz

unread,
Jul 1, 2009, 11:03:18 AM7/1/09
to Firebug
FF: 3.5
FB: 1.4b3

The CSS problems happens here too :(
I upgraded to FF3.5 today, after it was officially out... and was
forced to use the last version of Firebug, so it can be compatible to
FF3.5...
the 'disappearing' selectors problem happens all the time, on every
page...
As advised in this thread I've tried creating a fresh new profile,
with no addons except for Firebug - didnt help...
I'm completely lost without Firebug, and I really want to stay up to
date with the latest version of FF...

What else can I try except creating a new profile?

Thanks in advance


On May 12, 7:11 pm, Kyle Hayes <mrkyleha...@gmail.com> wrote:
> Here is a screencast to show what is happening:http://screencast.com/t/omNzONF0hyz
>
> On May 12, 9:09 am, Kyle Hayes <mrkyleha...@gmail.com> wrote:
>
> > I'm very saddened to report that this did not work. I just now tried
> > it and I am getting the same issue as before.
>
> > On May 12, 8:50 am, johnjbarton <johnjbar...@johnjbarton.com> wrote:
>
> > > Try a new Firefox profile:http://groups.google.com/group/firebug/web/faq-about-firebug
> > > bet that fixes it.
>
> > > jjb
>
> > > On May 12, 8:48 am, Kyle Hayes <mrkyleha...@gmail.com> wrote:
>
> > > > FF v.3.0.10
> > > > FB v.1.3.3
>
> > > > All of the suddenCSSdebugging stopped working and I'm no longer able
> > > > to change properties on the fly. If I do try to change a property and
> > > > escape out of the editing, the selector disappears. There just seems
> > > > to be a lot of issues with theCSSpane all of the sudden.

johnjbarton

unread,
Jul 1, 2009, 11:10:09 AM7/1/09
to Firebug
This is fixed, but not released.

jjb

jitz

unread,
Jul 1, 2009, 11:29:57 AM7/1/09
to Firebug
That's great news!
thanks for giving me some hope :)

When is it planned to be released?


On Jul 1, 6:10 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> This is fixed, but not released.
>
> jjb
>
> On Jul 1, 8:03 am, jitz <jit...@gmail.com> wrote:
>
> > FF: 3.5
> > FB: 1.4b3
>
> > TheCSSproblems happens here too :(

brian.tully

unread,
Jul 1, 2009, 12:18:59 PM7/1/09
to Firebug
Great news. Thanks so much John. Any chance this fix will also be
ported back to v1.3.x?

johnjbarton

unread,
Jul 1, 2009, 12:37:01 PM7/1/09
to Firebug
Not by us. The problem only occurs on FF3.5 and Firebug 1.3 was not
developed for FF 3.5.

jjb

Jason Persampieri

unread,
Jul 2, 2009, 12:52:11 PM7/2/09
to Firebug
Just to confirm, 1.4b4 fixed the CSS problem for me.

Thanks, John!

meef...@googlemail.com

unread,
Jul 2, 2009, 6:40:24 PM7/2/09
to Firebug
Hey,

> Just to confirm, 1.4b4 fixed the CSS problem for me.
>

1.4.0b4 still does not work for us with Firefox 3.5 on Mac OSX 10.5.
I'm not sure
about the test case (because it happens on every page), but you can go
to http://www.mindvent.de,
inspect the logo and try to "hide" the "text-align" property of the
image(logo).

The complete definition of that css-part disappears. On the page
nothing is changed.
But if you reload that page, the changes to the css (like hiding text-
align) are applied,
and there's no way to restore the original page by reloading it. The
only thing you
can do is restart Firefox. ;-O

Greetings
Christian

johnjbarton

unread,
Jul 2, 2009, 7:29:59 PM7/2/09
to Firebug
I tried to reproduce this:
1) http://www.mindvent.de/
2) Inpsect mindvent image, src=mindvent.gif.
"This element has no style rules"
So I can do anything about text-align.

jjb

On Jul 2, 3:40 pm, "meefs...@googlemail.com" <meefs...@googlemail.com>
wrote:
> Hey,
>
> > Just to confirm, 1.4b4 fixed the CSS problem for me.
>
> 1.4.0b4 still does not work for us with Firefox 3.5 on Mac OSX 10.5.
> I'm not sure
> about the test case (because it happens on every page), but you can go
> tohttp://www.mindvent.de,

meef...@googlemail.com

unread,
Jul 3, 2009, 4:57:14 AM7/3/09
to Firebug
Hi John,

Ok, maybe I was too fast, and I did the second check on a more
simple html page with the img element, those only style is the
text-align property of the surrounding <CENTER>-Tags.

So, actually I encountered two different bugs:

First Bug:
===========
Go to http://mindvent.de/bug.php
You should see an almost blank page with a text
inside a div "This is a test for _firebug_".

Inspect the span containing the underlined "firebug" text.
You should see this: http://mindvent.de/fbug/screen1.png

Now scroll down inside the Style view to the inherited style
of the center tag (see http://mindvent.de/fbug/screen2.png).
And then try to disable the "text-align: center".

After you've done this, the style for the center tag is completely
removed. The page itself didn't change. Now reload the page. You
should see this: http://mindvent.de/fbug/screen3.png

Now you can reload the page as often as you want. There's
no way to recover to the original state. Additionally every other
page using the center-tag is now left aligned (e.g. Google,
see http://mindvent.de/fbug/screen4.png) The only thing you
can do is restarting Firefox.
===========


Second Bug:
=============
Go to http://www.smashdown.net
Inspect the #indexHeader div (the only containing the
logo image). See http://mindvent.de/fbug/screen5.png

Remove the "font-family" style from #indexHeader. Then
remove the "font-size" attribute. After removing "font-size"
the #indexHeader "title" in the style section disappears,
the "font-size: 12px" attribute is still there, altough we've
removed it (see http://mindvent.de/fbug/screen6.png).

And now try to remove "font-size: 12px" again. The #indexHeader
section in the Style-view is removed completely and the design
is broken (see http://mindvent.de/fbug/screen7.png).
============


Hope this helps,
Kind regards
Christian

Livingstone Fultang

unread,
Jul 3, 2009, 3:30:24 AM7/3/09
to Firebug

> Just to confirm, 1.4b4 fixed the CSS problem for me.

- Windows Vista, Windows 7
- FF3.5
- FB.1.4b5

Problem still exist. It actually crashes my browser if i refresh the
page and try to edit the same element more than once!

Mark Vaughn

unread,
Jul 3, 2009, 3:20:49 AM7/3/09
to Firebug
Not working for me :(
FF 3.5
FB 1.4.4b

johnjbarton

unread,
Jul 3, 2009, 12:08:57 PM7/3/09
to Firebug
Hi Christian.

The first bug is known to us, but we can't fix it easily. The problem
is that you have change a "user-agent" style sheet given by Firefox.
Unfortunately edits on the user-agent style sheet seem to alter
Firefox directly. We don't know how to prevent this. At least we
should prevent edits on user agent style sheets.

The simple way to avoid this problem is to uncheck the Style side
panel option "Show User Agent CSS". Then those tempting entries will
not be shown and you can't edit them.

Of course you will say "But I want to see all of the CSS", Which is
why we did not simply remove the Show User Agent CSS feature once we
realized that edits would fail.

In other words, we don't have the resources to make a correct fix yet,
so we left a dangerous but useful feature in place rather than remove
it.

I'll ask the Firefox team to see if there is a fix from their side.

I could not reproduce the second problem, I guess it could be the same
reason. Please try unchecking the Style panel option Show User Agent
CSS and let us know if that fixes the problem. (If you have edited the
User agent CSS, you have to exit and restart Firefox).

jjb

On Jul 3, 1:57 am, "meefs...@googlemail.com" <meefs...@googlemail.com>
wrote:
> Hi John,
>
> Ok, maybe I was too fast, and I did the second check on a more
> simple html page with the img element, those only style is the
> text-align property of the surrounding <CENTER>-Tags.
>
> So, actually I encountered two different bugs:
>
> First Bug:
> ===========
> Go tohttp://mindvent.de/bug.php
> You should see an almost blank page with a text
> inside a div "This is a test for _firebug_".
>
> Inspect the span containing the underlined "firebug" text.
> You should see this:http://mindvent.de/fbug/screen1.png
>
> Now scroll down inside the Style view to the inherited style
> of the center tag (seehttp://mindvent.de/fbug/screen2.png).
> And then try to disable the "text-align: center".
>
> After you've done this, the style for the center tag is completely
> removed. The page itself didn't change. Now reload the page. You
> should see this:http://mindvent.de/fbug/screen3.png
>
> Now you can reload the page as often as you want. There's
> no way to recover to the original state. Additionally every other
> page using the center-tag is now left aligned (e.g. Google,
> seehttp://mindvent.de/fbug/screen4.png) The only thing you
> can do is restarting Firefox.
> ===========
>
> Second Bug:
> =============
> Go tohttp://www.smashdown.net
> Inspect the #indexHeader div (the only containing the
> logo image). Seehttp://mindvent.de/fbug/screen5.png
>
> Remove the "font-family" style from #indexHeader. Then
> remove the "font-size" attribute. After removing "font-size"
> the #indexHeader "title" in the style section disappears,
> the "font-size: 12px" attribute is still there, altough we've
> removed it (seehttp://mindvent.de/fbug/screen6.png).
>
> And now try to remove "font-size: 12px" again. The #indexHeader
> section in the Style-view is removed completely and the design
> is broken (seehttp://mindvent.de/fbug/screen7.png).

meef...@googlemail.com

unread,
Jul 4, 2009, 11:19:38 AM7/4/09
to Firebug

Hi John,

> The first bug is known to us, but we can't fix it easily.
> In other words, we don't have the resources to make a correct fix yet,
> so we left a dangerous but useful feature in place rather than remove
> it.

Ok, I understand that. For me it's a valid solution to disable user-
agents CSS,
at least as long as it is too much work to fix the Firefox problem in
Firebug.

> I could not reproduce the second problem, I guess it could be the same
> reason. Please try unchecking the Style panel option Show User Agent
> CSS and let us know if that fixes the problem. (If you have edited the
> User agent CSS, you have to exit and restart Firefox).

I just disabled the user-agent CSS feature and tried again, but the
problem still persists. I've checked it with Firebug 1.4.0b5. Maybe
it's only reproducable on Mac OS X (10.5.7) ? Firefox is 3.5.,
Gecko/20090624?

A friend of mine is having the same problems on his Mac.

Kind regards
Christian

johnjbarton

unread,
Jul 4, 2009, 11:31:47 AM7/4/09
to Firebug
Boris Zbarsky on the Firefox team gave me some info on how to fix
this. I'll try to get it for the next 1.5 release and 1.4.1 if that
works.

jjb

On Jul 4, 8:19 am, "meefs...@googlemail.com" <meefs...@googlemail.com>
wrote:
Reply all
Reply to author
Forward
0 new messages