Groups
Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
Groups
Chromium Extensions
Conversations
About
Sort By Relevance
Sort By Date
1–30 of many
Chris Zalcman
, …
Oliver Dunk
5
Jul 7
Why Chrome recommends to remove featured extensions?
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
unread,
Why Chrome recommends to remove featured extensions?
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
Jul 7
Dan Ridd
, …
Rudy Jdira
5
Jul 2
chrome.storage.managed policy values not applying to Chrome extension
>>
Manifest
(
v3
) includes: “storage”: { “managed_schema”: “schema.json” } >> >> schema.json at the package root: { “type”: “object”, “properties”: { “apiKey
unread,
chrome.storage.managed policy values not applying to Chrome extension
>>
Manifest
(
v3
) includes: “storage”: { “managed_schema”: “schema.json” } >> >> schema.json at the package root: { “type”: “object”, “properties”: { “apiKey
Jul 2
Oliver Dunk
2
Jun 20
Re: [crx] Chrome Crash When Calling chrome.sidePanel.open with windowId: chrome.windows.WINDOW_ID_CURRENT After Dynamically Requesting sidePanel Permission
extension using
Manifest
V3
. >>> The crash happens immediately after the chrome.sidePanel.open call, and no >>> specific error message is logged before the
unread,
Re: [crx] Chrome Crash When Calling chrome.sidePanel.open with windowId: chrome.windows.WINDOW_ID_CURRENT After Dynamically Requesting sidePanel Permission
extension using
Manifest
V3
. >>> The crash happens immediately after the chrome.sidePanel.open call, and no >>> specific error message is logged before the
Jun 20
Liang Cui
, …
Oliver Dunk
45
May 30
Allow string script in chrome.scripting.executeScript()
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
unread,
Allow string script in chrome.scripting.executeScript()
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
May 30
Yixian Wang
,
Patrick Kettner
3
May 21
Feature Badge Rejection for Extension Without Clear Reason
>>
Manifest
V3
is used. >> - >> >> A Privacy Policy is provided. >> - >> >> Only required permissions (cookies, storage) are requested
unread,
Feature Badge Rejection for Extension Without Clear Reason
>>
Manifest
V3
is used. >> - >> >> A Privacy Policy is provided. >> - >> >> Only required permissions (cookies, storage) are requested
May 21
A.S
,
Oliver Dunk
2
May 20
Are we allowed to remotely fetch ".onnx" format files?
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
unread,
Are we allowed to remotely fetch ".onnx" format files?
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
May 20
Pawel Kacprzak
, …
Álvaro Stagg
20
Apr 2
Manifest V3: service worker not registered in popular extension
The extension's
manifest
version. >>>>>>>>>>> * The type of background context used (persistent page, event >>>>>>
unread,
Manifest V3: service worker not registered in popular extension
The extension's
manifest
version. >>>>>>>>>>> * The type of background context used (persistent page, event >>>>>>
Apr 2
Daniel Martin
, …
Patrick Kettner
3
Apr 2
What reasons should I give my offscreen document?
upgraded to
manifest
v3
, and part of >> that involved moving some calls that I had done on a background page to an >> offscreen page. >> >> Specifically, my
unread,
What reasons should I give my offscreen document?
upgraded to
manifest
v3
, and part of >> that involved moving some calls that I had done on a background page to an >> offscreen page. >> >> Specifically, my
Apr 2
Svyatoslav Alekseev
, …
woxxom
13
Mar 27
MV3: Failed to send SharedArrayBuffer to Offscreen Document
done in
manifest
.json if I remember >>> correctly, try googling. >>> On Saturday, March 22, 2025 at 7:55:35 PM UTC+3 Svyatoslav Alekseev >>> wrote:
unread,
MV3: Failed to send SharedArrayBuffer to Offscreen Document
done in
manifest
.json if I remember >>> correctly, try googling. >>> On Saturday, March 22, 2025 at 7:55:35 PM UTC+3 Svyatoslav Alekseev >>> wrote:
Mar 27
Adrien C.
,
Peter Bloomfield
4
Mar 25
Deploying an extension using blocking webRequest without GPO
keep a
Manifest
v2 version of our extension on the Chrome Web Store >>> so that those clients are currently installing it using Registry's >>> HKLM/SOFTWARE
unread,
Deploying an extension using blocking webRequest without GPO
keep a
Manifest
v2 version of our extension on the Chrome Web Store >>> so that those clients are currently installing it using Registry's >>> HKLM/SOFTWARE
Mar 25
guillaume olivieri
,
Oliver Dunk
4
Mar 13
Issue with Chrome Tab Audio Capture : can't maintain both playback and transcription
> *
manifest
.json*{ >>> "name": "Audio Capture Test", >>> "description": "Records tab audio with transcription
unread,
Issue with Chrome Tab Audio Capture : can't maintain both playback and transcription
> *
manifest
.json*{ >>> "name": "Audio Capture Test", >>> "description": "Records tab audio with transcription
Mar 13
Craig
,
Patrick Kettner
2
Mar 11
Possible to use Appcheck verified backend?
Requirements for
Manifest
V3
:* > > - *Violation:* > Including remotely hosted code in a
Manifest
V3
item. > - *Violating Content:* > - *Code snippet:* popup.js: gapiScript
unread,
Possible to use Appcheck verified backend?
Requirements for
Manifest
V3
:* > > - *Violation:* > Including remotely hosted code in a
Manifest
V3
item. > - *Violating Content:* > - *Code snippet:* popup.js: gapiScript
Mar 11
Karan Goraniya
, …
Cuyler Stuwe
8
Mar 5
Next.js 15 + TypeScript Chrome Extension CSP Issue Issue
Hello Cuyler, Good point! In that case, which React framework would be the best fit for a Chrome extension? On Monday, February 24, 2025 at 8:45:29 PM
unread,
Next.js 15 + TypeScript Chrome Extension CSP Issue Issue
Hello Cuyler, Good point! In that case, which React framework would be the best fit for a Chrome extension? On Monday, February 24, 2025 at 8:45:29 PM
Mar 5
Vinod Kumar
, …
Oliver Dunk
4
Mar 3
Changes in background script files are not picked by the manifest V3 browser extension
design of
Manifest
V3
and would make the experiences > much more similar. > Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, > GB > >
unread,
Changes in background script files are not picked by the manifest V3 browser extension
design of
Manifest
V3
and would make the experiences > much more similar. > Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, > GB > >
Mar 3
Manish Golcha
,
Oliver Dunk
2
Feb 25
Manifest V3, Dynamic code execution
and since
Manifest
V2 will > soon be deprecated, I'll be using
Manifest
V3
. However, I have some > specific requirements that I haven't been able to fully address yet
unread,
Manifest V3, Dynamic code execution
and since
Manifest
V2 will > soon be deprecated, I'll be using
Manifest
V3
. However, I have some > specific requirements that I haven't been able to fully address yet
Feb 25
Vinod Kumar
,
woxxom
3
Feb 25
Content scripts policy violated for hrefs with javascript:fn in manifest v3
failing in
manifest
v3
when the anchorElement is having >> href="javascript:somefn()" >> >> Error - >> "Refused to run the JavaScript
unread,
Content scripts policy violated for hrefs with javascript:fn in manifest v3
failing in
manifest
v3
when the anchorElement is having >> href="javascript:somefn()" >> >> Error - >> "Refused to run the JavaScript
Feb 25
Oscar Lima
,
Oliver Dunk
2
Feb 24
Chrome Extension gradual rollout / feature flags
extension uses
Manifest
V3
, I cannot use remotely hosted code, > which would have made implementing feature flags easier. Given this > restriction: > > 1. *Is there a way
unread,
Chrome Extension gradual rollout / feature flags
extension uses
Manifest
V3
, I cannot use remotely hosted code, > which would have made implementing feature flags easier. Given this > restriction: > > 1. *Is there a way
Feb 24
Rahul Raman
,
Oliver Dunk
9
Feb 24
Manifest V3 - Intercept request in flight
achievable in
manifest
v3
Yes. In fact, this is not possible in *both*
Manifest
V2 and
Manifest
V3
. For using native proxy as you suggested, will it be like this ? - extension > redirects
unread,
Manifest V3 - Intercept request in flight
achievable in
manifest
v3
Yes. In fact, this is not possible in *both*
Manifest
V2 and
Manifest
V3
. For using native proxy as you suggested, will it be like this ? - extension > redirects
Feb 24
aoyu
,
Oliver Dunk
3
Feb 23
Manifest V3 - Unable to get any permissions
is my
manifest
.json and the details of my extension, i can't seem to >> figure out why everything else on the
manifest
.json is applying but my >> permissions are not
unread,
Manifest V3 - Unable to get any permissions
is my
manifest
.json and the details of my extension, i can't seem to >> figure out why everything else on the
manifest
.json is applying but my >> permissions are not
Feb 23
Cae Rule
, …
Patrick Kettner
6
Feb 20
Manifest v2 Sunset June 2025 and webRequestBlocking for Enterprise
removed for
manifest
V3
was done for years at this point, and will continue to not be supported. The pieces that you mentioned are supported a
manifest
v3
, and will continue to be supported
unread,
Manifest v2 Sunset June 2025 and webRequestBlocking for Enterprise
removed for
manifest
V3
was done for years at this point, and will continue to not be supported. The pieces that you mentioned are supported a
manifest
v3
, and will continue to be supported
Feb 20
Jahfari Coumarbatch
,
Oliver Dunk
2
Feb 19
Chrome Notifications API
you using
Manifest
V3
? If so, the suggested approach would be to open an offscreen document and call the audio APIs from there: https://developer.chrome.com/docs/extensions/reference
unread,
Chrome Notifications API
you using
Manifest
V3
? If so, the suggested approach would be to open an offscreen document and call the audio APIs from there: https://developer.chrome.com/docs/extensions/reference
Feb 19
Likely Logic
, …
woxxom
11
Feb 18
User Scripts vs injected scripts with eval()
workarounds for
v3
look a bit convoluted and bonkers, but I'll try them out in due course, and assuming they do the trick, all I have to do is wait for direct execution in mv3 in a couple
unread,
User Scripts vs injected scripts with eval()
workarounds for
v3
look a bit convoluted and bonkers, but I'll try them out in due course, and assuming they do the trick, all I have to do is wait for direct execution in mv3 in a couple
Feb 18
Tom Brothers
, …
Oliver Dunk
3
Feb 17
CSP errors driving me insane, hours of wasted time
documentation for
Manifest
V3
? https://firebase.google.com/docs/auth/web/chrome-extension In particular firebase/auth/web-extension is specifically designed to work
unread,
CSP errors driving me insane, hours of wasted time
documentation for
Manifest
V3
? https://firebase.google.com/docs/auth/web/chrome-extension In particular firebase/auth/web-extension is specifically designed to work
Feb 17
Ken Morse
, …
Oliver Dunk
14
Feb 12
Account verification for chrome extensions should include voice
have a
manifest
v2 we need to update. >> >> We don't mind at all providing a valid, reachable and public phone number >> but we are completely stuck because there
unread,
Account verification for chrome extensions should include voice
have a
manifest
v2 we need to update. >> >> We don't mind at all providing a valid, reachable and public phone number >> but we are completely stuck because there
Feb 12
Oliver Dunk
, …
Tom Doan
12
Mar 17
PSA: userScripts.execute() and multiple world support in User Scripts API
API in
Manifest
V3
, we heard > from many developers that they often need to inject a script based on a > user action. This was not easy to do with the existing API which required >
unread,
PSA: userScripts.execute() and multiple world support in User Scripts API
API in
Manifest
V3
, we heard > from many developers that they often need to inject a script based on a > user action. This was not easy to do with the existing API which required >
Mar 17
Oliver Dunk
Jan 16
PSA: Updated frame matching behavior in `chrome.scripting` API
scripts in
Manifest
V2. Now, frames are matched with the `match_origin_as_fallback ` logic implemented in
Manifest
V3
. This means both frames would be included by default. This follows
unread,
PSA: Updated frame matching behavior in `chrome.scripting` API
scripts in
Manifest
V2. Now, frames are matched with the `match_origin_as_fallback ` logic implemented in
Manifest
V3
. This means both frames would be included by default. This follows
Jan 16
Robert James Gabriel
, …
Alex
9
Jan 14
Blog Post: How I would Improve The Chrome Webstore.
given us
Manifest
V3
... https://www.eff.org/deeplinks/2019/07/googles-plans-chrome-extensions-wont-really-help-security On Tuesday, January 14, 2025 at 10:04:08 AM
unread,
Blog Post: How I would Improve The Chrome Webstore.
given us
Manifest
V3
... https://www.eff.org/deeplinks/2019/07/googles-plans-chrome-extensions-wont-really-help-security On Tuesday, January 14, 2025 at 10:04:08 AM
Jan 14
Klyra
,
Oliver Dunk
5
Jan 9
Looking for guidance – Why didn’t my extension get the Featured Badge?
built using
Manifest
V3
as required. >>>> The only possible reason I can think of is that the extension icon >>>> doesn't match the icon at the top of the
unread,
Looking for guidance – Why didn’t my extension get the Featured Badge?
built using
Manifest
V3
as required. >>>> The only possible reason I can think of is that the extension icon >>>> doesn't match the icon at the top of the
Jan 9
Ethan Ferrari
, …
Gaurang Tandon
17
Jan 6
Extension does not initialize after upgrade to Manifest V3... in non-US regions
/ /
manifest
.json page was accessible, but its DevTools Console was empty (it had no logs). When we ran await chrome.runtime.getContexts({}) in its console, it showed only one context
unread,
Extension does not initialize after upgrade to Manifest V3... in non-US regions
/ /
manifest
.json page was accessible, but its DevTools Console was empty (it had no logs). When we ran await chrome.runtime.getContexts({}) in its console, it showed only one context
Jan 6
Evan Cohylakis
, …
hrg...@gmail.com
10
12/23/24
Manifest V2 phase-out - "short time" explanation
uses a
manifest
2, and recently (it was >>>>>>>>> yesterday) I had to manually enable it since google chrome says " This >>>>>
unread,
Manifest V2 phase-out - "short time" explanation
uses a
manifest
2, and recently (it was >>>>>>>>> yesterday) I had to manually enable it since google chrome says " This >>>>>
12/23/24