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!

Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

firebug breakpoints

  • 1 odpověď
  • 1 má tento problém
  • 1 zobrazení
  • Poslední odpověď od 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

Všechny odpovědi (1)

the-edmeister
the-edmeister
  • Moderator
more options

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