Avatar for Username

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

firebug breakpoints

  • 1 resposta
  • 1 tem este problema
  • 5 visualizações
  • Última resposta de 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

Todas as respostas (1)

the-edmeister
the-edmeister
  • Moderator
more options

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