webextensions.api.userScripts - Chrome now supports userscripts about browser-compat-data HOT 2 OPEN

The userScripts API currently documented on MDN is Firefox's original userScripts API, consisting of the user_scripts manifest key and the userScripts.register method. The userScripts API that Chrome supports is a new API behind the "userScripts" permission and several other methods, completely including a userScripts.register method with a different signature. This new API was designed in the WECG at w3c/webextensions#279, and Chrome was the first to implement it. In Firefox we are currently looking into scheduling the implementation work of the new API.

To clarify the documentation, let's introduce the distinction between the "old" API (userScripts.register methid taking an object and returning a promise resolving to an object with the unregister method, only available to MV2 extensions with the user_scripts manifest key) and the new/standard API (userScripts.register method taking an array of RegisteredUserScript objects and returning an empty promise). Note: confusingly Firefox's return value (with the unregister method) is also called RegisteredUserScript. Let's emphasize that RegisteredUserScript.unregister is Firefox-only.

from browser-compat-data.

The bug tracking Firefox's implementation of the userScripts API is at https://bugzilla.mozilla.org/show_bug.cgi?id=1875475

from browser-compat-data.