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
Due to MV3, we can't spin up web workers from background scripts and due to cross-origin policies, we also can't spin up the web worker if we're running it within a content script on another origin, e.g. let's say this is a youtube extension, the content script wouldn't be able to spin up the web worker there as it'll
This makes it seem that for browser extensions that use MV3, there isn't a way to run the web worker unless we're running the extension on origins that we specifically own and can modify the content policy. Am I missing something here? I've gone down a huge rabbit hole today trying to get PGlite working on my extension and due to this limitation it feels like it won't work and, due to the limitations of MV3, can't work. Is this correct? Would be great to get a second opinion here on whether this is true and if so add it to the docs so others know not to try this out. Thanks
The text was updated successfully, but these errors were encountered:
So, I could be wrong here but as I understand it:
This makes it seem that for browser extensions that use MV3, there isn't a way to run the web worker unless we're running the extension on origins that we specifically own and can modify the content policy. Am I missing something here? I've gone down a huge rabbit hole today trying to get PGlite working on my extension and due to this limitation it feels like it won't work and, due to the limitations of MV3, can't work. Is this correct? Would be great to get a second opinion here on whether this is true and if so add it to the docs so others know not to try this out. Thanks
The text was updated successfully, but these errors were encountered: