Huh. So you think the DOMContentLoaded event is now firing before ALL GM scripts get run?
Ok, so I basically cloned this script to one for an extremely basic page I use as a homepage to hold like a dozen links and refreshed... a lot. Results: It fires MAYBE one out of every three times. The question now becomes: why the heck is DOMContentLoaded firing so early, and/or why are GM scripts running so late? And is there a way to change the latter? Like, why is it suddenly only getting invoked well after DCL is fired, when pre-the latest update it was working 100% of the time? (Note: I tried adding a @run-at document-start to the super-basic test version, which improved it to maybe 60-70%% success rate, but that's counter-indicated in the docs for GM 4. With @run-at document-end clocked in around the same 60% ish success) On Tuesday, November 14, 2017 at 4:49:09 PM UTC-5, Anthony Lieuallen wrote: > > On Tue, Nov 14, 2017 at 4:23 PM, Steven O'Donnell <[email protected] > <javascript:>> wrote: > >> ... >> The DOMContentLoaded event apparently never fires. Same across a bunch >> of scripts. Started when I updated to FF 57. >> > ... >> > > Much more likely, it has already fired for this document, before this > script started running. > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
