Yes, it's actually the combination of you removing the previous alert() AND RESTARTING. It's a FF 4.0 issue, where an alert causes setTimeOut to not to work, and after that it doesn't work even without the preceding alert() UNTIL you restart FF. See
https://bugzilla.mozilla.org/show_bug.cgi?id=647727 On Mar 13, 1:12 am, rveach <[email protected]> wrote: > Ok, I guess this can be ignored. > I tried disabling NoScript even though the whole page was enabled, and > the Request worked. > I then tried enabling NoScript again, and the Request still worked.... > > The only thing I can think of is that somehow restarting Firefox > between the enabling/disabling fixed the issue. -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" 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/greasemonkey-users?hl=en.
