Thanks for the quick reply, Anthony. I've filed a bug at bugzilla.mozilla.org about this issue.
https://bugzilla.mozilla.org/show_bug.cgi?id=548145 On Feb 23, 5:31 pm, Anthony Lieuallen <[email protected]> wrote: > On 02/23/10 16:41, Fracture wrote: > > > I'm guessing that Firefox/Greasemonkey doesn't fully destroy the old > > page environment until the next page is drawn, so when you go back to > > the old page, it loads it from memory/cache > > This is called "fastback". > > > another load event is > > fired, and Greasemonkey applies the script again. Perhaps this is a > > bug in Firefox itself, and the extra load event should not be fired. > > Yes, it shouldn't fire DOMContentLoaded if it didn't load the DOM (but > rather restore the fastback cached version). -- 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.
