There's always a workaround... ;-) Thanks for the tip! I just want to be sure whether this is a undesired collateral effect or an intentional modification. In other words: should I expect you to rollback this modification or get used to this behavior?
On Apr 9, 4:51 pm, Erik Vold <[email protected]> wrote: > This is because of the fix to issue > 1082http://github.com/greasemonkey/greasemonkey/commit/7de04f6ec9948a444c... > I think. The reason for the change was to prevent site owners from > being able to disable userscripts from running on their pages, so I > think it's a good change that should stick around.. if you script > wrights want to fix your userscripts asap, then do one of the > following in your user script(s): > > Option 1: > document.addEventListener("DOMContentLoaded", function() { > // my user script guts go here > > }, false); > > Option 2: > window.addEventListener("load", function() { > // my user script guts go here > > }, false); > > If you want to see the order that events are fired now, use this user > script:http://gist.github.com/361483 > > On this page:http://erikvold.com/tests/greasemonkey/DOMContentLoaded/index.cfm > > To summarize though it goes like this now: > > 1. run userscript on DOMContentLoaded event, on capture. > 2. page's DOMContentLoaded event listeners > 3. userscript's DOMContentLoaded event listeners > 4. page's load event listeners > 5. userscript's load event listeners > > Erik -- 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.
