Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

firebug breakpoints

  • 1 wótegrono
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót 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šykne wótegrona (1)

the-edmeister
the-edmeister
  • Moderator
more options

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