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

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

firebug breakpoints

  • 1 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: 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

すべての返信 (1)

the-edmeister
the-edmeister
  • Moderator
more options

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