Yes, you are correct, it does answer the question. Perhaps I should have said, it doesn't answer the question *well*.
Due to the number of programming layers involved, dealing with greasemonkey scripts is not a trivial issue. I dealt with the same page flicker question when I first started out, and I got really tired of being given a link to that stupid f'in wiki page that seemed to say that there was a workaround. Sure, there's a workaround, but it's not really feasible to ask everyone installing your script to screw with their usercontent file. Would have saved me hours of frustration if someone had just said NO instead of linking to that stupid f'in wiki page. So I apologize if it seemed I was saying your answer was wrong, it wasn't. I have no issues with your answer, but I obviously have issues with that stupid f'in wiki page =] Oh and I'm on board with BD... I have no problem wasting my time reading and posting comments on forums, but I've never edited a wiki page in my life and I'm not about to start. On Jul 14, 1:45 pm, Matt Sargent <[email protected]> wrote: > Actually, it does answer the question, in the very first sentence: > "The code in a Greasemonkey user script gets invoked when the > DOMContentLoaded event fires." > > Obviously, if you want to do something before the content is loaded, > Greasemonkey is not the answer. > > metzgerite wrote: > > That wiki page doesn't really answer the question. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
