Most existing .user.js engines should abort installation altogether. If they don't then it will make it too wide and match on every site. I assume that Greasyfork may have an issue with their detections as well if this change in behavior comes to fruition.
Btw current Chrome and Chromium native .user.js parsing (e.g. no Tampermonkey) comes back with an error message of:
Most existing .user.js engines should abort installation altogether. If they don't then it will make it too wide and match on every site. I assume that Greasyfork may have an issue with their detections as well if this change in behavior comes to fruition.
Btw current Chrome and Chromium native .user.js parsing (e.g. no Tampermonkey) comes back with an error message of:
Cc: @Sxderp, @JasonBarnabe
Ref(s):