John, Honza, Thanks for all the help so far, I've achieved the first major milestone. I now have a Firebug extension which tracks and consolidates network, DOM and JavaScript activity into a single representation.
The following is a screenshot of how it looks so far: http://www.filedropper.com/second/dfabbbd43bc9f80c27da19e28f5c6427.png blue = network activity (AJAX request in this case) purple = Javascript green = DOM events Current Status: Demo quality and requires a hack to get the JS call tracing. To avoid the Firefox crash which happens when we try to match the browser tab for the stack frame, I prevented firebug from trying to extract this information thereby restricting my addon to working with a single context. Unfortunately, this issue remains a showstopper and will likely prevent my addon from being released if it doesn't get addressed. Next steps: 1. Ability to save the trace information to a file (need to settle on some type of xml format) 2. Improve the UI and make it leverage other Firebug panels such as "Net" and "Script" for e.g. when you double-click a network trace it switches to the "Net" panel and displays the details. 3. Possibly add a side panel to display more details about the individual trace items. 4. Options to enable/disable the tracing and configuration options w.r.t monitoring DOM events. 5. Performance issues. Any comments/suggestions are welcome. Regards, Manoj On Dec 8, 5:47 pm, Manoj <[email protected]> wrote: > I've also posted this issue in the JS discussion group incase anyone > there has pointers. > > http://groups.google.com/group/mozilla.dev.tech.js-engine/browse_thre... > > Regards, > Manoj > > On Dec 5, 5:47 pm, Manoj <[email protected]> wrote: > > > Thanks John! > > Once this is working, it would be exactly what I need. > > > I'll try to spend sometime next week to figure out why FF is crashing. > > > Regards, > > Manoj > > > On Dec 4, 10:17 pm, John J Barton <[email protected]> wrote: > > > > Well I have good news and bad news. > > > > The good news is that in theory "traceAll()" from R1479 on branches/ > > > firebug1.4 is what you want. It filters the functionHook calls to > > > allow any from the URLs on the context and none others, then turns on > > > the call back. > > > > The bad news is that the code crashes > > > FF3.0.4.http://crash-stats.mozilla.com/report/index/18be1d90-ff17-4a14-a9f1-a... > > > I'll see if I can find a workaround. > > > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
