Bug when disabling CSS properties in the style pane (1.9.2)

140 views
Skip to first unread message

mirmir

unread,
May 24, 2012, 6:48:54 AM5/24/12
to Firebug
There seems to be a bug in the style pane when disabling CSS
properties. It doesn't always manifest itself from start, but when it
does it wont go away unless Firefox is restarted.

It manifests itself by the disappearance of the entire rule block from
the style pane when disabling any property of that block. Sometimes
the appearance of this anomaly is preceded by a different anomaly
which is the replacement of all rule blocks for the selected HTML tag
with a message saying that the tag has no CSS rules connected to it.

This problem makes Firebug very difficult to use for CSS debugging, to
the point of being useless for this purpose. Has anyone else
experienced this problem?

Sebo

unread,
May 24, 2012, 7:05:50 AM5/24/12
to fir...@googlegroups.com
Do you have a test case? Do you have any other extensions installed?
The only problem with disappearing styles I see is issue 5204.
Also a rule just disappears from the Style side panel when I change the selector so that it's not matching the element anymore. (Which is correct.)

Sebastian

mirmir

unread,
May 24, 2012, 12:40:44 PM5/24/12
to Firebug
On 24 Maj, 13:05, Sebo <sebastianzart...@gmx.de> wrote:
> Do you have a test case? Do you have any other extensions installed?

Yes, I have a few other extensions. I'll try to disable them and also
make a test case.

> The only problem with disappearing styles I see is issue 5204<http://code.google.com/p/fbug/issues/detail?id=5204>

It doesn't look like the same problem because whole rule blocks
disappear not single properties.

> Also a rule just disappears from the *Style* side panel when I change the
> selector so that it's not matching the element anymore. (Which is correct.)

I don't change selectors.
Message has been deleted

innundo

unread,
Jun 5, 2012, 9:11:44 AM6/5/12
to Firebug
Exactly the same problem here. Installing Firebug 1.9.2 over 1.9.1
didn't help. Reinstalling the Firebug (1.9.2) resolved the problem :)

Sebastian Zartner

unread,
Jun 5, 2012, 11:44:52 AM6/5/12
to fir...@googlegroups.com
Exactly the same problem here. Installing Firebug 1.9.2 over 1.9.1
didn't help. Reinstalling the Firebug (1.9.2) resolved the problem :)
Thanks for the info! Mirmir, does reinstalling also fix the problem for you?
If not, please follow the steps described in our wiki and tell us if that fixed the issue.

Sebastian

Sebastian Zartner

unread,
Jul 3, 2012, 4:31:13 AM7/3/12
to fir...@googlegroups.com
Thanks for the test case files. Though unfortunately I still can't reproduce the problem.

My steps:
  1. Opened Firebug on the test page
  2. Switched to the HTML panel
  3. Inspected the <h1> element
    ⇒ The Style side panel showed two rules, h1, h2, h3, h4, h5, h6 and body (inherited from body) (OK)
  4. Reloaded the page
    ⇒ The Style side panel still showed the two rules (OK)
  5. Disabled the color property of the h1, h2, h3, h4, h5, h6 rule
  6. Inspected the <h2> element
    ⇒ The Style side panel still showed the two rules (OK)
Did you already try to reproduce that problem on a fresh Firefox profile with just Firebug installed?
Can you provide clear steps like I gave them, which reproduce the problem?

Sebastian

Rocky

unread,
Jul 3, 2012, 12:11:52 PM7/3/12
to fir...@googlegroups.com
I also tested with a fresh Firefox Profile, but I made a mistake by including the <script> tag in the test HTML file.
  1. Remove line 9 "<script> </script>" from test.html
  2. Open Firebug on test.html
  3. Inspect <div class="header">, and disable background-color  OK 
  4. Reload page
  5. The rule .header disappears in the Style Panel (sometimes it reappears after 5 seconds)  BAD 
  6. Inspect <h1>, and disable color. Rule for h1 disappears in Style Panel and doesn't update the Browser View  BAD 
Hopefully that was a better explanation.
-rocky

Sebastian Zartner

unread,
Jul 4, 2012, 7:36:23 AM7/4/12
to fir...@googlegroups.com
Thanks for the steps. I can now reproduce that problems. I created issue 5654 to cover that.

Sebastian
Reply all
Reply to author
Forward
0 new messages