all scoped to YouTube (manifest v3). Would appreciate any update on the status and how we can get it over the line. Extension ID (jfabmmckbhkgecbigkcchmjbcmcomjnd) Thanks Faraaz

review since 8th April. It's been 16 days. Permissions are storage, tabs, and alarms all scoped to YouTube ( Manifest V3). Would appreciate any update on the status. Thanks, Faraaz

policies, manifest v3 standard, no unnecessary permissions, no malicious code, single purpose, complete privacy policy and user instructions. I have double checked all policy

compliant with Manifest V3 and have updated our privacy justifications. I have tried creating support tickets. All I am getting is are automated replies with no real discussion or

Regarding the manifest references to localhost and testapp, that was an >> oversight on my part; I was not building the manifest separately at build >> time for different

recently using Manifest V3. > > Both were built to solve personal pain points, and I'm especially > interested in > feedback around: > - MV3 best practices >

using *Manifest V3* and trying to > achieve *page-action–like behavior* (enable the extension only on > specific pages). > > I'm using chrome.declarativeContent

codebase follows Manifest V3 guidelines. >>>>>>>>>>>>> Permissions are restricted to YouTube pages, and the extension's purpose

mv3/manifest/incognito >>>> >>>> On Sunday, January 18, 2026 at 6:04:52 AM UTC+3 al wrote: >>>> >>>>> @woxxom >>

Extension (Manifest V3) that automatically triggers Picture-in-Picture (PiP) for YouTube videos when the user switches to a different tab, and exits PiP when they return. The Problem

Extension (Manifest V3) using Transformers.js v3 + ONNX > Runtime Web Running in an Offscreen Document (required for > WASM/WebGPU) 3 models total: > SmolLM2-360M (Text

extension using Manifest V3, and I would like to >> integrate the Google Picker API to allow users to choose a folder on Google >> Drive before uploading a file. >>

update the manifest from your own code? You could create a new directory with the correct files and then call launchPersistentContext afterwards. Oliver Dunk | DevRel, Chrome Extensions

entirely on Manifest V3 and declarativeNetRequest. >> >> I am currently advising several municipalities that are still relying on >> legacy extensions (like

> In Manifest V3, if I declare: >> *optional_host_permissions": [ "file://*/*" ]* >> >> is that enough to make the *“Allow access to file URLs

if the manifest does not have a update_url defined. It doesn't have to be a real location... but you need something there for it to be registered for updates. Then you can override

it to v3. Conversion was succesfull and its fully >>>>>> functional in v3. However some external customers are getting the issue of >>>>>>

Extension (Manifest V3)? >>>>>>> 2. >>>>>>> >>>>>>> For implementing this kind of reactive UI, should I

TypeScript and Manifest V3 - Uses Chrome's Translator API for text translation - Uses Language Detector API for automatic language detection - Privacy-focused: processes text

in a Manifest V3 item." You cleary know where you found this in the code, why not just share this in the rejection report? For a precvious violation, I had to email support and wait

extension (Manifest V3) where I: >>> >>> 1. >>> >>> Capture the current tab using chrome.pageCapture.saveAsMHTML from >>> the

a Chrome Manifest V3 extension in the Web Store that is used by K–12 school districts and force-installed via the Google Admin Console. We need to support managed configuration using

extension to Manifest v3. My team has spoken to them in the past, and they confirmed they were in process of completing this migration, so hopefully it will be live soon. On Mon, Jul 14

in a Manifest V3 item."* >>>>>>> >>>>>>> This was unexpected. We haven't added any externally hosted scripts. >>

updated to manifest v3 a long time ago, so it looks like it's a chrome update bug. On Fri, Jul 4, 2025 at 4:25 PM Oliver Dunk wrote: > The only time this message is used is when we disable

>> Manifest (v3) includes: “storage”: { “managed_schema”: “schema.json” } >> >> schema.json at the package root: { “type”: “object”, “properties”: { “apiKey

extension using Manifest V3. >>> The crash happens immediately after the chrome.sidePanel.open call, and no >>> specific error message is logged before the

difference between Manifest V2 and Manifest V3 here so it does sound like something else is wrong. Without seeing a full example, it's hard to help. Would you be able to put together

>> Manifest V3 is used. >> - >> >> A Privacy Policy is provided. >> - >> >> Only required permissions (cookies, storage) are requested

policies in Manifest V3: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements/ We do allow for remote configuration, as long as the full set of behaviors