We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

firebug breakpoints

  • 1 wotmołwa
  • 1 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot the-edmeister

wbgillis
wbgillis
more options

What's gone so wrong with FireBug version 2? The last version of 1 blows it away with performance, response, handling, debugging, EVERYTHING. But, I can't run v1.x with the later versions of FireBug. Why is that? Is this a forced upgrade to Firebug 2.x?

With Firebug 2.x:

- breakpoints don't work worth a d*mn. - jumping into/over/out-of debugging doesn't work worth a d*mn. - searching javascript used to, by default, search ALL the javascript files. Now it seems to set the default different and only recently did it seem to provide an option I have to MANUALLY SET EACH TIME to search all javascript files. - overall, debugging is sluggish, non-responsive, and at times flat out doesn't even work (can't set/clear breakpoints, the debugger-to-source code line is off so much it's ridiculous, e.g. iterating through loops it needs several F10s to get through one line, the debugger goes to bracket lines, and more)

Overall, FIREBUG NOW SUCKS. And, it was the best debugger out there. What has gone so wrong???

Thank you, Ben Gillis

What's gone so wrong with FireBug version 2? The last version of 1 blows it away with performance, response, handling, debugging, EVERYTHING. But, I can't run v1.x with the later versions of FireBug. Why is that? Is this a forced upgrade to Firebug 2.x? With Firebug 2.x: - breakpoints don't work worth a d*mn. - jumping into/over/out-of debugging doesn't work worth a d*mn. - searching javascript used to, by default, search ALL the javascript files. Now it seems to set the default different and only recently did it seem to provide an option I have to MANUALLY SET EACH TIME to search all javascript files. - overall, debugging is sluggish, non-responsive, and at times flat out doesn't even work (can't set/clear breakpoints, the debugger-to-source code line is off so much it's ridiculous, e.g. iterating through loops it needs several F10s to get through one line, the debugger goes to bracket lines, and more) Overall, FIREBUG NOW SUCKS. And, it was the best debugger out there. What has gone so wrong??? Thank you, Ben Gillis

Wšě wotmołwy (1)

the-edmeister
the-edmeister
  • Moderator
more options

Support for Firebug is over here: https://groups.google.com/forum/#!forum/firebug