告诉Firebug在任何Javascript被执行后很快就会破坏

Question

I've inherited a pile of code that's doing unexpected things when I click on some <button> elements.

The page has a lot of Javascript, and it's unclear what, if any, events have been setup on the button or its parent elements. I'm trying to find where execution starts so I can debug what's going on.

Is there a way to have Firebug (or any Javascript debugger) break whenever any javascript code is executed? Maybe someway to setup a break point on each line programmatically? Or is there some other way to find out which event the button is responding to (page users boh Prototype, jQuery, and some custom Javascript. I know.)

Answer 1

Just press Pause button on the firebug panel (on the left-top corner of it, two yellow vertical lines, when Script tab selected) - and it will stops at first JS string.

But it will stop JS executing really at ANY event - so if you have a button which catches mouse move and mouse click - i will not be able to stop on mouse click, since script will be stopped at mouse move each time you try to move mouse over this button. I suggest you just to insert alert()'s in the suspicious places - after some iterations you will found exactly string you need (where error occurs).

Answer 2

Close the Internet browser and open it again. "Break on next" will start working again. Otherwise Firebug simply ignores this option after a while, and doesn´t break but run javascripts for all events without warning you.

Answer 3

I found a bookmarklet that will list all bound events in your page .

This kind be useful if you don't know what events are bound by third-party code.

Answer 4

如果您想查看页面上设置的事件，您也可以尝试使用Eventbug 。

Answer 5

If this is a generic debugging problem you can use the Web Inspector in Safari / Chrome. An added bonus is that you can throw the following statement into your JavaScript code to pull up the debugger:

...
debugger; // Will trigger the debugger
...

Otherwise you can set breakpoints, conditional breakpoints, pause on the next execution, and all the usual tricks. Some nice videos are available here .

In response to the alert suggestion before. I would seriously recommend using console.log or console.dir if you have access to a debugger. You will get more information without blocking your script's execution. Also, don't forget that that console.log can take multiple parameters so you can nicely print out data, you don't have to constrain yourself to a single string like alert .