Toggle Element State with Google Chrome and Mozilla Firefox

By  on  

It's much easier to debug CSS than JavaScript since there are many fewer interactions in CSS, and they are much easier emulate. Still, element state debugging isn't simple...until now. Google Chrome's WebInspector and Mozilla Firefox's Firebug have a really sweet feature I just discovered which allows the developer to apply element states for the sake of debugging.

Chrome's WebInspector

Chrome CSS Element State

The image above displays Chrome's "Toggle Element State" button, allowing developers to toggle CSS states via checkboxes.

Firefox's Firebug

Firefox CSS Element State

The image displays Firebug's likewise menu, triggered by the down arrow on the CSS tab for an element.

This allows active CSS state bugging vs. simple CSS explorations to be much, much easier. Happy CSS debugging!

Recent Features

Incredible Demos

  • By
    LightFace:  Facebook Lightbox for MooTools

    One of the web components I've always loved has been Facebook's modal dialog.  This "lightbox" isn't like others:  no dark overlay, no obnoxious animating to size, and it doesn't try to do "too much."  With Facebook's dialog in mind, I've created LightFace:  a Facebook lightbox...

  • By
    Multiple Background CSS Animations

    CSS background animation has been a hot topic for a long time, mostly because they look pretty sweet and don't require additional elements.  I was recently asked if it was possible to have multiple background animations on a given element and the answer is yes...with...

Discussion

  1. Bruno Seixas

    Great tip, thanks =)

  2. FireBug does this for years. Just click the little arrow next to the style tab. It’s only :hover and :active, though.

  3. Hott Dogg

    The only thing Chrome cant do with states is when I need to debug an element that matches selector parentElement:hover element, for example
    Chrome applies states only to selected element in inspector and when you selected another element, selected state is applied to new element

  4. Next challenge: Debug pseudo elements with web inspector :p

    • the Chrome web inspector already supports pseudo elements.

      Under the Matched CSS rules is a Psuedo element
      I believe the latest version of firebug does similar, but I’m not sure as I haven’t used it in ages

    • Unfortunately you can not select the pseudo element like any other DOM-Element. Technically this is perfectly valid since pseudo-elements are not part of the DOM but I often miss that feature. Pseudo-elements are harder to debug than necessary.

  5. Good stuff, from what I know this has been around for a while already.

    @JAN BECK – not that hard really, you just have to select the main element and scroll down in the inspector panel to see the psuedo elements

  6. Daniel

    it’s also possible to do this with Firefox’ built in developer tools :-)

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!