[Greasemonkey] Re: Gm Bug in Firefox 1.5.0.4

[Bill Donnelly]

I don't understand that, but maybe I don't have to.

What mechanism does Gm use now to tell if it has already been loaded
into a page? Does it do some sort of a URL comparison? Does it check
to see if it is in a different window/tab? (like a "window id")

I remember back when that there were some problems with scripts being
called twice, or more, and you fixed it somehow to stop it from doing that.
And I remember seeing some code that looked like it was doing some sort
of a check to make sure it wasn't being reloaded when it was already loaded.
(it has become so complex now, though, that it is diffcult for me to
understand what is happening, since I haven't been in on the development
particulars since all of the 'security upgrades' and sandbox stuff, etc.)

I guess the question is, is Gm being called for the new window and it
thinks it doesn't need to be "reloaded" because it's already been loaded,
or is it not being informed at all that a new window needs to be "Gm'd"?
I suppose there could be some third case.

Also, on my system, "new windows" are loaded into tabs, if that makes
a difference.

I may take another shot at looking at the code to see if I can see
anything, but I'm not confident that I can understand all of the complexity
involved in these newer versions in the down deep underworkings of it all.

I'm just kind of hoping you will get an "Oh! That might be the problem"
reaction from the ideas I'm throwing out.

Aaron Boodman wrote:
> Hmm.. sounds like something that should be reported to mozilla as a bug.
>
> On the other hand, there's no reason to do all this. You can just
> manipulate the document (theWindow.document) directly -- you don't
> have to wait for the script to get executed again i the other window.
>
> make sense at all?
>
> - a
>