from a manifest v2 to manifest v3 extension >>>>> a few weeks ago. One of the main changes on the browser side is that the >>>>> background script used

function in manifest v3. Of course I got streamID using tabCapture api, but only capture() function is not available in service worker... in background.ts file, got streamID and sent

in the manifest will allow you to still use > chrome.webRequest.onAuthRequired only ( > https://bugs.chromium.org/p/chromium/issues/detail?id=1135492#c93). For >

a > manifest v3 service worker. I'd gotten it working while having the service > worker devtools open the whole time. Then I tested it with devtools > closed, and... there

submit a manifest v3 version of our extension. That said, there remain a couple of significant warnings on the screen so hopefully by the time trader verification becomes a requirement

thinking around Manifest V3, and as part >>>>>> of that, we just published an update to the Known Issues page: >>>>>> https://developer.

> (Manifest V3) that is functioning as expected under normal circumstances. >>> However, I have encountered an issue when integrating this extension with a >>

their Chrome manifest v3 extension to Safari. Whatever I do with manifest in Safari I'm getting an content_security_policy error when first api call is called: *Refused to connect

Thanks for the report! Would you be willing to share what your extension is? Doing this on a simple extension is not replicating it, so I would love to

CSP in Manifest V3. In that case, you could >>>>>> consider loading them in a sandboxed frame (different to the `sandbox` >>>>>> attribute

Requirements for Manifest V3 >> >> section says (highlights mine): >> >> Execution of logic from a remote source is permissible only when >>>

I'm also interested to hear any news/information about this since I am starting to hear reports about SWs not starting with no explanation for my

, and Manifest V2 is no longer under active development, it's unlikely to be something we change. Please do share any use cases you have though if this is causing you trouble. We'

Requirements for Manifest V3:* >>> >>> * Violation:* >>> >>> Including remotely hosted code in a Manifest V3 item. >>> >>

>> Manifest V3's shift from localStorage to the Chrome Storage Area, >>>>> addressing the lack of direct inspection tools for this storage in the >

and using manifest v3. > Curious what changes were made to it so that it would work with the new > restrictions. > > I added the following userscript, and it successfully

docs to manifest v3 >>>> >>>> On Monday, December 19, 2022 at 8:09:51 PM UTC Denis L wrote: >>>> >>>>> I still miss clear examples

> to manifest v3, even though 99% of our code is identical. Whatever limit >> we're hitting seems to have been higher for manifest v2 extensions. >> >> On

in your manifest.json and >> others. You can find them by using a utility or a nodejs package that >> checks the public suffix list. >> >> On Monday, July 15

On Sat, Jul 6, 2024 at 1:20 AM Oliver Dunk wrote: > This chromium-extensions list is a public one mostly used for announcements and questions from

> in Manifest V3. Are you seeing the same and if so could you look at > changing that? > > Thanks, > Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome

the extension's manifest: >>>> >>>> ``` >>>> "background": { >>>> "service_worker": "

submitted the Manifest V3 version of my extension for approval and >>> chose the option so that it's NOT immediately published upon approval, so >>> that I

that until Manifest V2 is no longer supported for all > users. > Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, > GB > > > On Tue

have a manifest v2 Chrome extension that uses *blocking* chrome. >> *webRequest*.onHeadersReceived to rewrite part of the Location header on >> responses from a matching

develop/manifest-v3-migration-guide/ , >> the "Event-driven background scripts" section. The article describes a lot >> of the initialization of the

to use Manifest V3, no permissions changes, added required privacy policy info, and changed a bit of code to use fetch. I was hoping for a quick review since I've got a super simple

> running Manifest V3 > > > According to this site , 45% > of the web store is still on MV2. > The fact that an extension hasn't been updated recently doesn'

migrating from Manifest V2 to Manifest V3. So, we >>>>>>> removed one message type from both the content script and the service >>>>>>

" to manifest.json so that older browsers won't update the extension. On Wednesday, May 29, 2024 at 7:26:55 PM UTC+3 Vibhash Chandra wrote: > Hi, > > What's