[Greasemonkey] DOM Inspector & greasemonkey

[Aaron Boodman]

It sounds like you guys are talking about different things.

If Greasemonkey changes the content dom (or the chrome dom
inadvertently for that matter :-)) you will see it in DOM inspector.

You will *not* see the Greasemonkey script itself in the DOM inspector
(as a script tag or whatever) because Greasemonkey scripts are not
added to any DOM to be evaulated.

Does that answer everyone's question?

- a

On 4/6/06, Rod McGuire <mcguire at telerama.com> wrote:
> Quoting Jeremy Dunck <jdunck at gmail.com>:
> > On 4/6/06, Rod McGuire <mcguire at telerama.com> wrote:
> > > GM is not run in the DOM browser so of course you won't see the effects of
> > your
> > > script there.
> >
> > Huh?  Are we all talking about the DOM Inspector which ships as part
> > of FF?  GM does run in a page context, and the DOM Inspector does show
> > a page's live DOM.
> >
> GM *does* run under standard DOM inspector? It never has for me. I run Win XP
> pro SP2. Do other people with my setup have GM scripts show up in the DOM
> inspector? If so, is there anything special I have to set?
>
> Right now the Javascript console gives the error messages:
>  No chrome package registered for
> chrome://communicator/content/utilityOverlay.xul
>  No chrome package registered for chrome://communicator/content/tasksOverlay.xul
> _______________________________________________
> Greasemonkey mailing list
> Greasemonkey at mozdev.org
> http://mozdev.org/mailman/listinfo/greasemonkey
>