Well, I think you've got the picture upside down ;-). You see it's not like I know how to set a breakpoint in a source imported or how to get that source or even for that matter what you mean by imported. There is no list of ways JS scripts are loaded and no documentation on any of them.
So we can handle inline script, included scripts, eval scripts, event scripts, scripts injected by tags, and by document write (sorta). Each case was by trial and error. Or rather by error then trial. Once we have a test case, I can see how to make it work. jjb On Dec 22, 3:10 pm, Alberto Santini <[email protected]> wrote: > On Dec 22, 11:10 pm, John J Barton <[email protected]> > wrote: > > > My guess is yes, if not I can fix it if I had a test case. > > I read your usefull > tutorialhttp://getfirebug.com/chromebug/usingChromebug/t1/index.html > > It would be usefull (at least for me) a post about how to set a > breakpoint in a source imported, > or how to get that source. > > If I set the global scope to chrome://{extension}/content/browser.xul, > I can see only the sources loaded in the page, but some script imports > other sources. > > Of course, I have been missing something. > > > > > On Dec 22, 1:02 pm, Alberto Santini <[email protected]> wrote: > > > > Is it possible to see the JavaScript sources (in Chromebug) imported > > > with Components.utils.import from the extension? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
