Firebug Features Poll part 2 – The Unloved
This is the second part of the Firebug Features Poll (part 1 is here). This time, focusing on the answers to the question: What is your least favorite Firebug feature. The one you never use. I don’t know if the question was worded poorly or if people just felt like venting, but many of the responders didn’t limit themselves to just one thing. As a result, I had to modify my non-scientific methodology a little bit and count mentioned features as votes instead of just lumping the responses into a single feature bucket.
As in the previous poll, I added a Junk column for responses that didn’t really make sense. “I <3 Firebug!” is great to hear (and Firebug <3s you too!) but it wasn’t really useful for the purposes of this poll. Augmenting this column, I created another category for responses lamenting Firebug stability or specific missing features. This was tied for first place with the most votes.
Third place – Tie!
• Search feature
• Console. Surprised some people dislike the Console, but two of you did. One person mentioned a lot of exceptions coming from the browser showing up in the Console lowering the quality of information. These can often be cut down by unchecking the “Show Chrome Errors” and messages options in the Console’s mini-menu.
Second place – Tie!
These have the dubious distinction of having the same number of responses as the Junk column.
• CSS panel
• DOM panel
• Script panel — Responses varied from “I don’t know how to use breakpoints” to users who prefer using the Console to do printf-style interactive debugging. Other respondents claimed the script panel was just too buggy.
caveat: I believe there is probably more than one type of user of Firebug. Some of them may not be using Twitter and this poll might not have gotten to them. The types of users who replied and said that their favorite feature was the HTML Inspector and live-editing of CSS are probably the same group of people who don’t make heavy use of the Script debugger. If you’re a heavy debugger, please let us know in the comments.
• HTML node editor – If you double click on a tag in the HTML view, you’ll see the node editor. Clicking the “Edit” button or using the Escape key will get you out of it.
• Event logging – right click on a node in the HTML viewer and select “Log Events”. Now every mousemove, click and keystroke in that node will be registered in the Console. How can you not love that?
There were no votes(!) for the Net panel, so everyone clearly loves it and thinks it’s awesome.
• we need to work harder on bugfixes and stability. Spending a lot of effort on stability and usability would probably go a long way towards making Firebug a better, more pleasurable to use piece of software.
• The CSS and DOM tabs aren’t loved. Adding better navigation to the DOM page, or reworking it entirely might be useful. Getting rid of it and the CSS tab entirely could be another option but not one we’d consider doing without some very strong feedback from the community.
• Search feature was a bit of a surprise, but we’re improving that for version 1.5 so hopefully it becomes easier to use.
As before, please leave us your comments if you think we’re missing something.