1

Please see attached image for reference. Until very recently, Firebug add-on in Firefox would show a red error count on top right and the Console would have the javascript error info.

But looks like Firebug is no longer supported and is being integrated inside Developer Tools: https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug and for that link you'd see that the error count only could be now displayed but only after pressing Shift+F2 keys - and even then error info not displayed.

I would like to see the error count red as soon as the page loads. I'd also like to see error info in the 'errors' tab of the Console, as it used to be. I have looked for a solution - even tried to revert to older Firebug but so far no success.

Any idea?

Current Firefox/Firebug screen

Sebastian Zartner
  • 18,808
  • 10
  • 90
  • 132
IrfanClemson
  • 1,699
  • 6
  • 33
  • 52
  • Note, what you are seeing is *not* Firebug but the [Firefox DevTools](https://developer.mozilla.org/en-US/docs/Tools/) with a Firebug theme. This is because Firebug doesn't work together with [multi-process Firefox](https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox) and the Firebug button automatically toggles the DevTools instead of Firebug in that case. Read more about that on the [related Mozilla Hacks blog post](https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/). – Sebastian Zartner May 10 '17 at 22:04

2 Answers2

1

Your screenshot obviously shows the Firefox DevTools (with Firebug theme) and not the Firebug.

To see the JavaScript errors in the Web Console you need to toggle the related filter. To do that click the JavaScript errors filter button button in the console toolbar.

Having said that, there's a bug regarding the error count causing the number shown in the Developer Toolbar to be wrong, i.e. it often doesn't match the number of errors logged to the console.

Sebastian Zartner
  • 18,808
  • 10
  • 90
  • 132
  • Thank you. But, no, that error showing was not working for me. Before I did the fix per my own Answer here, the behavior was: I load a page; if it was missing a file to download (I know it's not javascript but still), then no red count would show. Even if I were to press the JS button. I am happy with reverting back and I hope Firebug/Web Developer Tools team would really look into these issues. – IrfanClemson May 11 '17 at 13:19
  • As I've noted, there's a bug, which causes the number of errors displayed in the Developer Toolbar to be incorrect. I've updated my answer to make it a bit more obvious. – Sebastian Zartner May 11 '17 at 14:14
  • Thank you. So I just undid my reversion, clicked on the Firebug icon on top to bring up the web console in the bottom of the browser, clicked on the JS panel to enable that, loaded that page which used to show an error about the missing image and still nothing--nothing on the top right FBug icon and nothing inside the Web Console. I have (again) implemented per my own Answer. The FBug inside the Developer Tool is not good my needs. – IrfanClemson May 11 '17 at 15:49
  • You should add a screenshot of the error you see in the Firebug console to your question. A missing image rather sounds like a network error rather than a JavaScript error. To see different kinds of errors you need to enable the other filters, too. Note, the Firebug icon generally does *not* show the number of errors anymore once multi-process Firefox is enabled. And also note that Firebug definitely stops working starting from Firefox 57, because [then Firefox only supports WebExtensions](https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/) (and Firebug isn't one). – Sebastian Zartner May 11 '17 at 20:43
  • Yes, it is a network error--a missing file. But the point is that old FireBug would immediately show such problems--whether network or javascript--on the Firebug icon on top right--even if FireBug was not launched. That immediately drew attention to some problem in the code. Similarly, while working on javascript code, any page reloads would show the errors on top right and inside the 'errors' panel a pretty detailed description of the error. With those two critical things gone I have to revert to the old FireBug. – IrfanClemson May 11 '17 at 20:52
  • 1
    Just tested it with again with a clean profile using Firefox 53.0.2 and Firebug 2.0.19 and the Firebug button doesn't show the error badge on anymore. Anyway, the Developer Toolbar is expected to show the error count (though currently has the aforementioned bug) and by default all filters to show errors are activated in the DevTools console. So, if you don't see the errors there even when all filters are activated, it's a bug and you should [report it](https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools%3A%20Console), so it can get fixed. – Sebastian Zartner May 12 '17 at 05:26
  • Thank you. FireBug is probably the #1 reason for developers to use FireFox. Indeed, against my corporate policy of only using IE (the horror!), I have been using FireFox because of FireBug. I hope the team realizes how serious this bug is. – IrfanClemson May 12 '17 at 12:50
0

Never mind,

Per this post: How to revert Firebug to old version?

I set all instances of browser.tabs.remote.autostart to false and Firebug seems to be working as it was before.

This maybe temp solution but it fixes my problem :)

HTH

Community
  • 1
  • 1
IrfanClemson
  • 1,699
  • 6
  • 33
  • 52