Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome Extension Manifest V3 Support #118

Open
GhazanfarKhan opened this issue Mar 14, 2024 · 2 comments
Open

Chrome Extension Manifest V3 Support #118

GhazanfarKhan opened this issue Mar 14, 2024 · 2 comments

Comments

@GhazanfarKhan
Copy link

GhazanfarKhan commented Mar 14, 2024

In manifest V2, extensions have the ability to run the Twilio Voice JS SDK in the background. But with the introduction of manifest V3 (MV3), running the Twilio Voice JS SDK in the background using service workers does not work out of the box due to certain limitations which include DOM access and the ability to keep the service worker alive.

What will be the flow to register worker events in service worker or offscreen api?

@ert3e
Copy link

ert3e commented Mar 22, 2024

In Chrome V3 u need to create a document by (chrome api) chrome.offscreen.createDocument() and in this document, u can run this SDK.

@ert3e
Copy link

ert3e commented Mar 28, 2024

In manifest V2, extensions have the ability to run the Twilio Voice JS SDK in the background. But with the introduction of manifest V3 (MV3), running the Twilio Voice JS SDK in the background using service workers does not work out of the box due to certain limitations which include DOM access and the ability to keep the service worker alive.

What will be the flow to register worker events in service worker or offscreen api?

So it's not an issue use chrome.offscreen document witch allows u to use doom, mate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants