Development Blog

getfirebug.com has Firebug 1.11a4

Firebug 1.11a4 fixes 16 issues.

Another great alpha from the Firebug team. See some highlights from this release:

• Panel for CSS Selector Queries
• Custom Firebug Commands
• Improved $ and $$ Commands

Panel for CSS Selector Queries

Firebug offers new side panel (available in the CSS panel) that allows quick execution of CSS selectors. The panel also shows the list of matching elements.

In order to see list of matching elements for an existing CSS rule, just right click on the rule and pick Get Matching Elements item. The list of elements (together with the CSS selector) will be displayed in the side panel.

Of course, you can also use custom CSS selectors. Just click on the yellow edit line at the top of the side panel and type your own selector.

This feature has been previously implemented in a separate SelectBug extension.

See more in Issue 5931

Custom Firebug Commands

Firebug offers fresh new API that can be used to register new commands for Firebug’s command line. Any Firebug extension can now implement and publish new commands.

Firebug.registerCommand("myCommand", {
    handler: function myCommandHandler(context, args) {
        return "Hello World!";
    },
    description: "My first Firebug command!"
});

That’s it! Such command can be executed in the Command Line as follows:

See more in Issue 5817

Improved $ and $$ Commands

Firebug also improves existing commands for querying DOM elements.

$() command uses querySelector()
$$() command uses querySelectorAll()

It also means that the argument passed in must be CSS selector.

So, for example, if you need to get an element with ID equal to “content” you need to use # character.

$("#content")

If you forget, Firebug will nicely warn you

See more in Issue 5764

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

This entry was posted on Friday, October 5th, 2012 at 8:57 am and is filed under Firebug Releases, Firefox. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.