The user script I use that still uses the old APIs is Webcomic Reader, if you’re wondering. I probably won’t bother unless I have a reason to switch away from Violentmonkey, though. However, it looks like Greasemonkey’s polyfill ( ) has expanded its support for the old `GM_…` functions since I last checked, so maybe migrating old scripts I use to Greasemonkey 4’s new API won’t be as difficult and limiting as the last time I considered it. There also used to be some functions such as `GM_registerMenuCommand` that Greasemonkey 4 provided no equivalent to. `GM.getValue`), and dropped support for the equivalent synchronous `GM_…` functions. Greasemonkey 4, released in 2017, introduced a new asynchronous API `GM.…` (e.g. I use Violentmonkey because unlike Tampermonkey, it’s open source, and unlike Greasemonkey, it supports old user scripts that use the synchronous `GM_…` functions such as `GM_getValue` and `GM_setValue`.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |