You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems currently a CSS file is always generated and I assume used in extensions with content scripts, though in some cases this is not needed. This seems to also require MAIN world scripts specify an extension ID which as far as Im aware is not truly required.
Ideally there should be no need for a CSS file to always be created and injected into the page. Removing this, should also allow the requirement of main scripts to specify an ID to be removed too.
The text was updated successfully, but these errors were encountered:
The current method has limitations since some extensions may be distributed outside the chrome store and currently it seems to be impossible to have anything in the MAIN World without the extension also being published or an account in the chrome store to get a key.
It seems currently a CSS file is always generated and I assume used in extensions with content scripts, though in some cases this is not needed. This seems to also require MAIN world scripts specify an extension ID which as far as Im aware is not truly required.
Ideally there should be no need for a CSS file to always be created and injected into the page. Removing this, should also allow the requirement of main scripts to specify an ID to be removed too.
The text was updated successfully, but these errors were encountered: