The "break on next" doesn't work that well. I have events for onHover and onClick on an element and with the "break on next', I can't use it to debug the onClick events, because the onHover event always fires first.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jan Odvarko Sent: Thursday, June 18, 2009 10:36 AM To: Firebug Subject: Re: Feature Request: Break on DOM Object Event I think you are looking for "Break on Next" feature (you need 1.4). Just click on the pause button available in Firebug toolbar (it should start flashing) and do something on the page (e.g. press a button), the debugger will break at the first executed javascript line. Anyway, I like the approach you have indicated. Just a few days ago we have been discussing how to further extend the current "Break on Next" with something like : Break on XHR, Break on CSS, etc.. Honza On Jun 18, 6:24 pm, AdamV <[email protected]> wrote: > Hey guys, > > I don't know if this is either possible or even reasonable but I'll > propose it anyways. > > Its not always feasible to put a breakpoint in the JavaScript source. > This is true, for instance, if you're working with third party code > (I'm running through the behaviour of a commercial CMS right now) or > if functions may have been overloaded. > > It would be nice if you could select an Element, and select an event > on which to start debugging. So I can select some button and start > debugging the click event. When the click event happens, the debugging > start. This would allow you to know ALL the functions that are called > by the event. > > Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
