Firebug 3, arrow key in autocomplete navigates only visible items, not all valid ones

[alfonsoml]

pick a property with number of different values and when the autocomplete popup shows, use the keyboard arrows to navigate them, instead of cycling through all the possible valid values like Firebug 2, in Firebug 3 it jumps back to the start of the list
being able to quickly test different values was one of the advantages of Firebug.

[Sebastian Zartner]

Another bug related to the DevTools (which Firebug 3 is based on). I've already reported that about a year ago. See bug 1097516.
This is a really bad UX and I'd like that to be fixed. Though note, that you can at least get the other values suggested by typing one or more characters.

Sebastian

[alfonsoml]

This lack of polish in DevTools is why so many of us didn't want to use them and kept using Firebug 2 as long as possible.
Now the best way to debug is go ahead and switch to another browser (which I was already doing for certain tasks, but now Firefox doesn't have any advantage over other browsers).

[Sebastian Zartner]

I agree with you that Firebug 2 still has a better UI than the Firefox DevTools, I'd even claim, better than any other browser devtools in some ways. Many of those little UX features will get lost with Firebug 3 but already have related bug reports and may be readded in future versions of Firebug or the DevTools.

Though, the Firefox DevTools have matured a lot the last years and are offering features you don't get in any other tool like e.g. the filters editor or the Animations side panel. And the DevTools team is listening to users via channels like the Firefox Developer Tools ideas page and other means to continuously improve their tools. So I strongly advocate for trying them out a little more and raising things you think could be improved.

Sebastian

[alfonsoml]

Yes, it might have things that no one else has, but if I don't ever plan to use them like the Audio editor and almost all those "exclusive", then all that work means zero to me.
Instead I need basic features and Firebug got them right in so many cases that the other tools usually just copied them. The only team that didn't look at Firebug was Firefox DevTools and so everything had to be redone again and then precious time is wasted because as we have been saying for years: we just want the Firebug features, there are lots of reports, listing of missing features, ... I don't feel the need to keep track of them.

[Sebastian Zartner]

The DevTools features are not restricted to those special case things like the Audio editor, which probably only use a handful of people (and which would better be put into an add-on, IMO), but they also do some things better than Firebug like the console message filtering for example.
If you followed the reports on Bugzilla and publications by the DevTools team, you'd see that they do look at Firebug (and other tools) while creating their features. There are other reasons why they didn't just integrate Firebug into Firefox. So, please don't claim things when you don't have any knowledge about the background!

Anyway, fact is, Firebug 3 will be mostly a theme for the DevTools besides adding a few features to them. Therefore, issues you see while using it, should also be checked when Firebug is disabled. If they still happen with the pure DevTools, you should open a bug report for them in Bugzilla, otherwise open the report on Firebug's issue tracker. If you don't do that, there's little chance those issues get recognized and fixed.

Sebastian