Closed jesus2099 closed 2 years ago
Reproduced on Android 9 Kiwi Browser 105.0.5195.33 Violentmonkey 2.13.1
I see several changes around run-at
, document-start
and document-end
in Violentmonkey V2.13.1 release notes… 🤔
Now also confirmed in Chrome 105.0.5195.127 (Build officiel) (64 bits).
I discovered that OK script must be put first in the list and NG script must be put second, to reproduce the bug!
The bug has been fixed by @tophf but we now have to wait for next Violentmonkey release.
I had my laptop reset. And since then I have some problems: #708, #709, #710
My userscripts with
// @require
libraries and without exactly// @run-at document-start
(either none or other value), have the libraries not loaded by Violentmonkey.This works with
// @run-at document-start
!?This does not work, the SUPER.js code is not append. I also tried
// @run-at document-ready
and// @run-at document-idle
both no good (NG), as well.Other values than
document-start
are blocking the@require
loading. OK script must be first in the list and NG script must be second in the list, to reproduce the bug. So maybe it's not only related torun-at
.I don't know what has changed except that I had to install programs as non-admin, in
%LocalAppData%\Programs\
(I don't remember previous versions)