Aha, nobody can say that Honza does not know everything, even the future ;o)
Honza has been working on an extension that reintroduces the events panel. You can get it from: http://getfirebug.com/releases/eventbug/1.5/eventbug-0.1b1.xpi But bear in mind that it is still in beta. - Mike Ratcliffe On Jan 20, 8:32 pm, mruhlin <[email protected]> wrote: > So, frameworks like jQuery are becoming more and more popular, and > making things less and less debuggable. > > Where I used to write code like: > <a href="#" onclick="alert('you clicked me');">click me</a> > > I'm now writing code like: > <a href="#" id="clickMe">click me</a> > <script> > $("#clickMe").click(function(){ > alert("you clicked me!");}); > > </script> > > And that's great. Separation of code and presentation, etc etc. > But it makes firebug less useful. If I'm fixing a bug where clicking > that link breaks things, I used to just be able to inspect it in the > DOM inspector, then go look for the function that it calls. Easy. > But now I have no idea what events are attached to that particular > link. Have to start grepping through code for the element's ID, or > maybe its class, etc etc. > > Would be great if Firebug added some features to help with this. > Anybody have any tips on better ways for me to approach the problem?
-- 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.
