persistent-serviceworker VS chrome-extensions-samples

Here you go persistent-serviceworker.

The ServiceWorker becoming inactive in 5 minutes per MV3 is a debacle. Workarounds exist and the code to implement keeping the ServiceWorker persistent, e.g., to stream live radio station from the ServiceWorker to the client winds up not saving any resources - we have to keep something running to keep the service worker running. You would be hard-pressed to count how many issues in the wild have been filed in multiple source code repositories just on that lack of functionality - for years now, e.g., Need help to understand and use this #2.

There are workarounds which involve using an iframe https://github.com/guest271314/persistent-serviceworker/tree/main/chromium_extension_web_accessible_resources_iframe_message_event or window.open() https://github.com/guest271314/sw-transfer-stream or and offscreen document https://github.com/guest271314/offscreen-webrtc with WebRTC - however that involves loading an entire HTML document, and each has its own deficienfies - with all of the Window features that we do not really need just to transfer data between the Web page I have control of and the ServiceWorker I have control of.

One approach for your requirement is to append an iframe with src set to an HTML document listed in "web_accessible_resources" to an arbitrary document and use postMessage() from the Web page to the iframe, then from the iframe to the MV3 ServiceWorker, see https://github.com/guest271314/persistent-serviceworker/tree/main/chromium_extension_web_accessible_resources_iframe_message_event.

See https://github.com/guest271314/persistent-serviceworker

Yes, it is possible to keep an extension or non-extension ServiceWorker persistent, active indefinitely https://github.com/guest271314/persistent-serviceworker.

If you host the HTML for and use "web_accessible_resources" in manifest.json the </code> can communicate directly with MV3 <code>ServiceWorker</code>. </p> <p>To keep MV3 <code>ServiceWorker</code> persistent see <a href="https://github.com/guest271314/persistent-serviceworker">https://github.com/guest271314/persistent-serviceworker</a>.</p> </div>

I utilize "web_accessible_resources" with an , where chrome.* API's are exposed, and does not become inactive.

Some workarounds to keep MV3 ServiceWorker active Persistent ServiceWorker.

You should be using the context menu API. You can check out some of the examples to have a better idea. This single file should get you all the info you need - context menu basic example.

Hell, I even included the fix for the broken Google Chrome chrome-extensions samples Python Native Messaging host in a PR I filed to update their sample https://github.com/GoogleChrome/chrome-extensions-samples/pull/617/commits/c26521ed60d6028dd73c84a2b726a1889b6616f7.

There are some examples here https://github.com/GoogleChrome/chrome-extensions-samples/issues/662 and here https://github.com/GoogleChrome/chrome-extensions-samples/issues/784.

What happens when you try to run this Native Messaging host application https://github.com/GoogleChrome/chrome-extensions-samples/blob/main/_archive/mv2/api/nativeMessaging/host/native-messaging-example-host on your current machine without modifying anything in the file or installing a package that links python to Python 2 and not Python 3?

Chrome Extension Examples - a collection of sample Chrome extensions to learn from

Another more involved challenge: Transfer (e.g., using Transferable objects) an ArrayBuffer from a ServiceWorker to an arbitrary Web page not controlled by or in the scope of the ServiceWorker - without using an element https://github.com/GoogleChrome/chrome-extensions-samples/issues/766.

You can use Native Messaging to connect to and communicate with a native host, e.g., Python, from JavaScript client in the browser, see https://github.com/GoogleChrome/chrome-extensions-samples/pull/617/commits/a06b4e37b7a095f845a321b0cd7adac5a3b41f02.

Take the time to carefully read this Google Chrome extension samples issue Sample: Transfer a blob from a background context to a page #766.

You can use declarativeNetRequest to remove content-security-policy for specific Web sites or all Web sites, see https://github.com/guest271314/remove-csp-header; https://github.com/GoogleChrome/chrome-extensions-samples/issues/662.