You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a very rare situation that is no longer covered by webext-dynamic-content-scripts. This is a long list of conditions that have to appear at the same time for the bug to appear:
You're on Chrome
Your manifest_version is 2
Your manifest has multiple objects inside content_scripts
Your content_scripts mentions the same file twice (for example to be injected onto multiple domains, via manifest)
Your content_scripts have one of run_at, exclude_matches, all_frames
Your other content_scriptsdo not have the same exact property
If this is happening, you should stay on v9 of this module until you upgrade to Manifest v3.
Here's an example extension affected by this limitation:
{
"manifest_version": 2,
"content_scripts": [
{
"all_frames": true, // Present here, missing from the next one"matches": ["https://example.com/*"],
"js": ["content.js"],
},
{
"matches": ["https://www.example.org/*"],
"js": ["content.js"],
}
]
}
The text was updated successfully, but these errors were encountered:
There's a very rare situation that is no longer covered by
webext-dynamic-content-scripts
. This is a long list of conditions that have to appear at the same time for the bug to appear:manifest_version
is2
content_scripts
content_scripts
mentions the same file twice (for example to be injected onto multiple domains, via manifest)content_scripts
have one ofrun_at
,exclude_matches
,all_frames
content_scripts
do not have the same exact propertyIf this is happening, you should stay on v9 of this module until you upgrade to Manifest v3.
Here's an example extension affected by this limitation:
The text was updated successfully, but these errors were encountered: