SW stops working in MV3

[Pavel Aronovich]

For some users, our extension stops working several times a day. The pop-up window opens, and SW stops responding to any events (for example, chrome.webNavigation.onBeforeNavigate or chrome.tabs.onUpdated). 

Restarting the browser helps. What can it be and where to look? 

Logs cannot be collected because SW is simply dead. The problem is not related to the extension update, it has not changed recently. We use a port (chrome.runtime.connect and chrome.runtime.OnConnect) to communicate SW and script content. And it looks like he's alive, a message from SW about establishing a connection comes. Yes, we do reconnect if the connection is broken and the page is still alive.

Thanks.

[Shu]

I got a similar problem, but when I opened extensions' page I saw like 30+ SWs for it, they were duplicated a lot. No problems before I updated the browser like a week ago or something like that

[Pavel Aronovich]

browser of the current version

вторник, 21 марта 2023 г. в 13:13:46 UTC+3, Shu:

[Pavel Aronovich]

The biggest question is how to understand what the problem may be and where to look when the problem is reproduced by the user? Maybe it's our mistake. Although this is unlikely, because the extension suddenly stops working.

вторник, 21 марта 2023 г. в 13:15:57 UTC+3, Pavel Aronovich:

[Zenitsu]

This is an intended behavior of MV3, unfortunately, the SW is killed after a certain amount of time, I think it's a bit after 20s of running, you cannot trust that your SW will be running endlessly.

if I remember correctly, you can wake up the service worker if you send a message to it https://developer.chrome.com/docs/extensions/mv3/messaging/ 

this is a very annoying behavior, but chrome said that this is intentional because many extensions were abusing background scripts to steal user data, etc etc

[Shu]

It can't be true, SW is waking up with " chrome.tabs.onUpdated" etc, and all of that was working last year

[Pavel Aronovich]

Yes, he falls asleep and that's understandable. 

SW should wake up automatically to events like chrome.webNavigation.onBeforeNavigate or chrome.tabs.onUpdated

вторник, 21 марта 2023 г. в 14:35:52 UTC+3, Zenitsu:

[Pavel Aronovich]

Interestingly, after a few hours, the user's extension worked correctly. Without restarting the browser.
It's not accurate yet, but clearing the browser cache may have helped.

вторник, 21 марта 2023 г. в 14:43:56 UTC+3, Pavel Aronovich:

[Oliver Dunk]

Hi Pavel,

This definitely doesn't sound expected. As you mentioned, events should wake the service worker.

One interesting place to check with issues like this is chrome://extensions-internals/. I'm not sure how useful it would be in this case, but it would at least be good to check that `event_listeners` is populated with the events you expect.

Beyond that, please do open a bug. As you hinted at, we have some existing ones like https://bugs.chromium.org/p/chromium/issues/detail?id=1271154 but nothing that exactly matches up with what you're describing as far as I can remember.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/8b433010-4812-4c11-bcab-53b2f05062d3n%40chromium.org.

[Pavel Aronovich]

Oliver, why do we see two almost identical lines here?

вторник, 21 марта 2023 г. в 15:43:40 UTC+3, Oliver Dunk:

[Pavel Aronovich]

The problem appeared again in the same user.

Checked chrome://serviceworker-internals/ - SW in RUNNING mode, but the Log is empty (it shouldn't be). SW is stuck and does nothing. If SW is forcibly stopped and started, then everything works.

Checked chrome://extensions-internals/ - all events are registered.

What to do, how to understand what the problem is?

вторник, 21 марта 2023 г. в 15:51:52 UTC+3, Pavel Aronovich:

[Oliver Dunk]

That's all super interesting! Thanks for taking the time to pull that together.

Could you open a bug and explain everything you've explained here, including that the service worker appears to be running but isn't responding?

I'm not familiar enough with some of the internals to know what the next best step is but I can ask one of our engineers to take a look.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Pavel Aronovich]

Yes, I will do it

вторник, 21 марта 2023 г. в 16:40:44 UTC+3, Oliver Dunk:

[Pavel Aronovich]

https://bugs.chromium.org/p/chromium/issues/detail?id=1426461

вторник, 21 марта 2023 г. в 16:40:44 UTC+3, Oliver Dunk:

That's all super interesting! Thanks for taking the time to pull that together.

[Oliver Dunk]

Thanks. I've updated the bug and I'll make sure to pass it along to the right people.

Please do share anything new you learn and I'll try to make sure we figure out the next steps soon :)

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Pavel Aronovich]

Thank you Oliver.
Unfortunately there is nothing new yet.

вторник, 21 марта 2023 г. в 17:30:15 UTC+3, Oliver Dunk:

[Pavel Aronovich]

silence everywhere... :(

вторник, 21 марта 2023 г. в 17:34:10 UTC+3, Pavel Aronovich:

[Tom Riley]

What would be great is if the "Update by March" (when it arrives) actually acknowledges that problems like this aren't an ideal environment to be committing to and includes something to reassure developers about moving extensions to MV3, rather that just being a "Sorry, but you've got no choice, anyway here's the new timelines we've decided."

[Hrishikesh]

Hi Pavel,

You could keep your SW awake by adding some useless pieces of code running with certain interval.

[Red ross]

What would be great is if the Chrome team can publish a guide / post-instructions on how to debug this specific issue and capture stats that can then help them resolve the same.

Waiting for a consistent repro as doesn't seem like a great option as similar issues have remained in limbo for a long time.

From both of these issues, i.e.:
1. https://bugs.chromium.org/p/chromium/issues/detail?id=1426461
2. https://bugs.chromium.org/p/chromium/issues/detail?id=1316588 

The symptoms are similar, i.e., Worker remains up and RUNNING (this is also what the workaround in the 2nd issue relies on)

Listeners stop responding, including:
- chrome.tabs.onUpdated (from #2)
- chrome.alarms.onAlarm.addListener (from #2)
- chrome.notifications.onClicked.addListener (from #2)
- chrome.notifications.onButtonClicked.addListener (from #2)
- chrome.browserAction.onClicked.addListener (from #2)
- chrome.contextMenus.onClicked.addListener (from #2)
- chrome.storage.local.onChanged

These bugs are also Pri 2 and 3 respectively, have we considered bumping the priority considering the amount of reports seeing similar issues here?
These extensions worked fine in MV2 before moving to MV3 so this seems like a regression in the platform and should be prioritised as such.

[Pavel Aronovich]

Hi Red ross,

I fully support your proposal. This problem is very critical!

I will try to implement similar to this:

https://bugs.chromium.org/p/chromium/issues/detail?id=1316588#c113

But this is a workaround that will not allow SW to fall asleep.

пятница, 24 марта 2023 г. в 11:49:45 UTC+3, Red ross:

[Pavel Aronovich]

There are many questions about the logic of SW operation. For example, there is a timer that fires once a minute. This is the normal behavior of the extension. 

SW wakes up every minute (restoring the state!) and then falls asleep after 30 seconds. 

Questions: why all this, what are we saving? Are you sure it hasn't gotten worse?

пятница, 24 марта 2023 г. в 12:01:37 UTC+3, Pavel Aronovich:

[Red ross]

With the MV3 timelines pushed back even further, hope seems rather dim for a fix.
There's seemingly total silence from the Chrome team on these issues.

[Simeon Vincent]

I've bumped 1426461 to P2 to match 1316588. I'll defer to the extensions team on whether the issues should be bumped higher.

With the MV3 timelines pushed back even further, hope seems rather dim for a fix.

I don't think the issue being discussed here and MV2 deprecation timeline have much overlap. I'm no longer part of the Chrome team, but based on my experience I suspect that the lack of updates is mostly a result of not having a way to reproduce and debug the issue. If the Chrome extensions engineers haven't experienced the issue, there's not much they can do beyond shrug and say "yeah, that's bad."

Since Chrome folks haven't been able to reproduce the extension background event dispatch bugs, I put together a list of suggestions on what the community could do to help gather more information about the bug in this comment.

If you've encountered a reproduction case where a Manifest V3 extension's background context is not processing events as expected, please perform the following reproduction steps to determine if it is a reproduction of issue 1271154 (this bug) or issue 1316588:

1. Note the ID of the extension.

2. Open chrome://serviceworker-internals and search for that extension ID.

2a. If you can find the extension's ID on this page and the URL listed under "Script:" matches the one declared in "background.servcie_worker" in the extension's manifest.json file, comment on issue 1316588 as described in Step 3.

2b. If the extension ID does not appear on this page, comment on issue 1271154 (this bug) as described in Step 3.

3. Add a comment to the relevant bug and include the following information.

* The extension's manifest version.

* The type of background context used (persistent page, event page, or service worker).

* The version listed on chrome://version (e.g. 104.0.5112.101).

* The name of your operating system.

* The version number of your operating system.

* A description of what happened before the extension stopped responding to events.

* Any additional information that you believe may might help identify the underlying issue.

* (optional) A redacted copy of the relevant extension object from the chrome://extensions-internals page.

* (optional) For those comfortable debugging Chromium, enable additional logging by following the guidance that appears after "I've uploaded a CL [1] with a smattering of various logs" in this comment: https://crbug.com/1316588#c68

Simeon - @dotproto

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/d20473a4-9da2-48b6-ad1c-46ab121053a2n%40chromium.org.

[Oliver Dunk]

Hi Red,

I'm definitely following that issue. I've also left another comment to hopefully keep things moving.

As Simeon mentioned, it can definitely be hard without steps to reproduce. That's not to say that we don't care about the issue, or think it's important to fix - we are just limited to asking questions and trying to understand what's happening.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Peter Bloomfield]

One of our developers recently saw something similar to this. He was working with Chrome (v112 I think) on macOS, with our extension whitelisted and loaded unpacked on the command line. He was viewing a webpage embedded in our extension (i.e. "chrome-extension://EXTENSION-ID/some-page.html). He quit the browser, then restarted it, and the embedded webpage reopened automatically. However, when he viewed our extension's info, it was somehow showing two service workers at the same time.

Our extension appeared to be working fine at first, until he closed the embedded webpage (other tabs were open so the browser was still running). At that point, one of the service workers disappeared, and our extension no longer responded at all. DevTools showed that the remaining service worker was still running; it just wasn't responding to events.

More importantly, the browser couldn't load any webpages after that. They all seemed to hang while loading. Our extension provides web-filtering, so we use the web request blocking events. My suspicion is that the browser was stuck waiting for our extension to handle those events. However, for some reason, our service worker wasn't receiving them.

Obviously the browser got itself into a bad state when it somehow created two service workers. My guess is that it basically terminated the wrong one when the embedded webpage was closed. It knew our extension was still running and that it was registered to receive certain events, but it was perhaps trying to send them to the wrong place.

Everything recovered when the browser was restarted again. I'm afraid we haven't been able to reproduce the problem though, and (as far as I'm aware) have never seen duplicate service workers at any other time.

[Simeon Vincent]

Peter, you noted that the developer "was viewing a webpage embedded in our extension." Did that page's script include service worker registration logic? I assume it did not, but I wanted to double check to make sure. For example:

if ('serviceWorker' in navigator) {

window.addEventListener('load', function() {

navigator.serviceWorker.register('/service-worker.js');

});

}

Also, you noted that you're using webRequstBlocking with a service worker based extension. Is this an MV2 or MV3 extension? If it's an MV3 extension, am I correct in assuming that you're force-installing it using enterprise policies?

Simeon - @dotproto

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/a49128f6-3f95-4b2b-871f-efc524f07fa5n%40chromium.org.

[Peter Bloomfield]

Hi Simeon,

The embedded page doesn't contain any worker registration logic. It's pretty simple. It just communicates with the extension service worker via sendMessage(), and displays some basic status info.

It's an mv3 extension, and we do force-install on customer systems in production. For development, we typically load the extension unpacked, but use command line option "--allowlisted-extension-id" to give it access to web request blocking.

[Oliver Dunk]

Thanks for sharing this Peter.

It definitely sounds like a race condition (two things tried to wake the extension on browser start, and two service workers were created).

Like with all of these issues it's hard to say if it will be reproducible but I'll have a play. Do let us know if you see anything like that again!

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Alexei]

More importantly, the browser couldn't load any webpages after that.

This sounds like https://bugs.chromium.org/p/chromium/issues/detail?id=1397879

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAOsQqB%3DOVp3ybdLxxrm0ymLWhyMDmhDXjyimYyrvsjLn5_63nw%40mail.gmail.com.

[Peter Bloomfield]

Thanks Alexei. We're definitely registering our web request event handlers during initial start-up. However, perhaps having a second instance of the service worker has a similar effect to registering asynchronously.

[Peter Bloomfield]

The duplicate service worker issue has happened here again. In this case, the same embedded webpage was open at the time, but closing it didn't make a service worker disappear.

This was on Chrome v 112.0.5615.138 (64-bit), running on Windows 11. As before, the extension was loaded unpacked, and allow-listed on the command line.

The service worker internals page showed both workers, where it normally only shows one:

Here's the relevant object from extension internals, in case it's useful:

{
   "creation_flags": [ "REQUIRE_MODERN_MANIFEST_VERSION", "ALLOW_FILE_ACCESS", "FOLLOW_SYMLINKS_ANYWHERE" ],
   "disable_reasons": [  ],
   "event_listeners": {
      "count": 39,
      "listeners": [ {
         "event_name": "identity.onSignInChanged",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "identity.onSignInChanged",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "identity.onSignInChanged",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onActivated",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onActivated",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onActivated",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "gcm.onMessagesDeleted",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "gcm.onMessagesDeleted",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "gcm.onMessagesDeleted",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "windows.onFocusChanged",
         "filter": {
         },
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "windows.onFocusChanged",
         "filter": {
         },
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "windows.onFocusChanged",
         "filter": {
         },
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "gcm.onMessage",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "gcm.onMessage",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "gcm.onMessage",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "omnibox.onInputChanged",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "omnibox.onInputChanged",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "omnibox.onInputChanged",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onCreated",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onCreated",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onCreated",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onUpdated",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onUpdated",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "tabs.onUpdated",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "windows.onCreated",
         "filter": {
         },
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "windows.onCreated",
         "filter": {
         },
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "windows.onCreated",
         "filter": {
         },
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "alarms.onAlarm",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "alarms.onAlarm",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "alarms.onAlarm",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "omnibox.onInputEntered",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "omnibox.onInputEntered",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "omnibox.onInputEntered",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "storage.onChanged",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "storage.onChanged",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "storage.onChanged",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "webRequest.onBeforeRequest/s1",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "webRequest.onBeforeRequest/s1",
         "is_for_service_worker": true,
         "is_lazy": true,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      }, {
         "event_name": "webRequest.onBeforeRequest/s1",
         "is_for_service_worker": true,
         "is_lazy": false,
         "url": "chrome-extension://bdfbaknfadcpbcggjiofpnfgiccknlpl/"
      } ]
   },
   "id": "bdfbaknfadcpbcggjiofpnfgiccknlpl",
   "keepalive": {
      "activites": [  ],
      "count": -1
   },
   "location": "COMMAND_LINE",
   "manifest_version": 3,
   "name": "Smoothwall Cloud Filter",
   "path": "D:\\source\\family-zone\\sw-cldflt-browser-extension\\dist",
   "permissions": {
      "active": {
         "api": [ "activeTab", "alarms", "gcm", "identity", "identity.email", "nativeMessaging", "storage", "tabs", "unlimitedStorage", "webNavigation", "webRequest", "webRequestBlocking", "system.memory", "scripting", "offscreen" ],
         "explicit_hosts": [ "*://*/*" ],
         "manifest": [  ],
         "scriptable_hosts": [ "*://*/*" ]
      },
      "optional": {
         "api": [  ],
         "explicit_hosts": [  ],
         "manifest": [  ],
         "scriptable_hosts": [  ]
      },
      "tab_specific": {
      },
      "withheld": {
         "api": [  ],
         "explicit_hosts": [  ],
         "manifest": [  ],
         "scriptable_hosts": [  ]
      }
   },
   "type": "TYPE_EXTENSION",
   "version": "0.2.13"
}

[Jovan Mihajlovic]

This happend to my extension as well. I have the luck that my extension should only run on one domain, so I set all related tab's discard property to false, this should help.

[Jovan Mihajlovic]

The property is autoDiscardable

[Joel mizael Bustos villaseñor]

Sent from my T-Mobile Device
Obtener Outloohttp://app.pathmatch.com/profile/joel-mizael-villasenork para Android

---

From: chromium-...@chromium.org <chromium-...@chromium.org> on behalf of Peter Bloomfield <peter.bl...@smoothwall.com>
Sent: Monday, April 24, 2023 5:00:29 AM
To: Chromium Extensions <chromium-...@chromium.org>
Cc: Peter Bloomfield <peter.bl...@smoothwall.com>; Alexei <alexeiaty...@gmail.com>; Chromium Extensions <chromium-...@chromium.org>; Simeon Vincent <sim...@chromium.org>; Pavel Aronovich <pave...@gmail.com>; Oliver Dunk <olive...@google.com>
Subject: Re: [crx] Re: SW stops working in MV3

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/9180dc23-19a1-42bc-b5a5-7840ac3fca53n%40chromium.org.

---

From: chromium-...@chromium.org <chromium-...@chromium.org> on behalf of Peter Bloomfield <peter.bl...@smoothwall.com>
Sent: Monday, April 24, 2023 5:00:29 AM
To: Chromium Extensions <chromium-...@chromium.org>
Cc: Peter Bloomfield <peter.bl...@smoothwall.com>; Alexei <alexeiaty...@gmail.com>; Chromium Extensions <chromium-...@chromium.org>; Simeon Vincent <sim...@chromium.org>; Pavel Aronovich <pave...@gmail.com>; Oliver Dunk <olive...@google.com>
Subject: Re: [crx] Re: SW stops working in MV3

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/9180dc23-19a1-42bc-b5a5-7840ac3fca53n%40chromium.org.