erosman
commented
1 year ago TBH, great many userscripts still use GM3 style code that was written for Firefox before version 57 (released 2017-11-14).
Tampermonkey & Violentmonkey, in order to keep compatibility with the old GM3 style userscripts that didn't update to GM4, implemented work-around.
There is a voluntary @compatible entry that can be added in userscript metadata block, and GreasyFork displays it on the script page (but only shows browsers).
:pushpin: There will be changes to the userscript environment in manifest v3 which will affect all user-script & user-style managers.
-
Simple YouTube Age Restriction Bypass
// @compatible chrome // @compatible firefox // @compatible opera // @compatible edge // @compatible safari
// @compatible chrome Only with Tampermonkey or Violentmonkey. Только с Tampermonkey или Violentmonkey.
// @compatible brave Only with Tampermonkey or Violentmonkey. Только с Tampermonkey или Violentmonkey.
// @compatible vivaldi Only with Tampermonkey or Violentmonkey. Только с Tampermonkey или Violentmonkey.
// @compatible edge Only in Edge 79+ with Tampermonkey or Violentmonkey. Только в Edge 79+ с Tampermonkey или Violentmonkey.
// @compatible firefox Only in Firefox 56+ with Tampermonkey. Только Firefox 56+ с Tampermonkey.
// @compatible opera Only with Tampermonkey. Только с Tampermonkey.
Will there be any meta to specify that the script is not compatible with FireMonkey to warn / alert the user? for example, if
//@FireMonkey-incompatible trueis added to the userscript, FireMonkey will make a prompt dialog to alert the user that the script which is going to install might not be fully compatible with FireMonkey, and confirm the user whether the userscript installation shall proceed or not.This is to avoid users to report the script that not working for them to the developer or to this GitHub. Those scripts were designed not to work in FireMonkey.