The alpha version of Firebug has a "break on next" feature (the pause button). This is very useful to see what is happening when you click on a button. "break on all errors" is also useful to debug these issues.
On May 7, 5:55 am, Ido <[email protected]> wrote: > Hey, > > I found that when I have problems with 'events' it's really hard to > debug them. > Would love to hear if someone have some methods (tips) to do it > better :) > Here is one example: > When you have such a selector (e.g. jQuery in this case) - $('form#div- > id #some-other-id') > and then you bind it to a click on a button - how can I trace the > click event and see WHY the selector is missing what I aim for? > > Thanks, > Ido --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
