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
The Chrome Web Store is introducing updates to our policies for extensions using MV3. These updates expand the possibilities to load remote content within your extension, while remaining in compliance with our remotely hosted code policies. Here is a guide on the changes and what they mean for your extension development:
Self-Contained Functionality: A Focus on Transparency
The core principle remains: the full functionality of your extension should be easily discernible from the submitted code. It is critical to ensure that the logic driving your extension is well-defined within its codebase.
External Resource Usage: Striking a Balance
Extensions can still reference and load data from external sources, but these resources must not contain any logic. Extensions are permitted to execute logic from remote sources only through documented APIs like the Debugger API and User Scripts API. This strikes a balance between flexibility and security, allowing external data without compromising the transparent nature of your extension's functionality.
Isolated Contexts: Exemptions and Responsibilities
Code running in isolated contexts, such as iframes and sandboxed pages, is exempt from certain restrictions on loading code from remote sources. However, it's crucial to maintain transparency. The full functionality of your extension should still be discernible in these contexts.
Review Process Consequences: A Note on Enforcement
If we are unable to determine the full functionality of your extension during the review process, we may take appropriate action. Submissions that lack clarity or violate policies might be rejected or removed from the Chrome Web Store.
You can learn more about today鈥檚 guidance in our Program Policies. These policy clarifications will go into effect on April 15, 2024. After that date, extensions in violation of these new policies may be removed from the Chrome Web Store and be disabled.
Cf email from Chrome:
Dear Developer,
The Chrome Web Store is introducing updates to our policies for extensions using MV3. These updates expand the possibilities to load remote content within your extension, while remaining in compliance with our remotely hosted code policies. Here is a guide on the changes and what they mean for your extension development:
The core principle remains: the full functionality of your extension should be easily discernible from the submitted code. It is critical to ensure that the logic driving your extension is well-defined within its codebase.
Extensions can still reference and load data from external sources, but these resources must not contain any logic. Extensions are permitted to execute logic from remote sources only through documented APIs like the Debugger API and User Scripts API. This strikes a balance between flexibility and security, allowing external data without compromising the transparent nature of your extension's functionality.
Code running in isolated contexts, such as iframes and sandboxed pages, is exempt from certain restrictions on loading code from remote sources. However, it's crucial to maintain transparency. The full functionality of your extension should still be discernible in these contexts.
If we are unable to determine the full functionality of your extension during the review process, we may take appropriate action. Submissions that lack clarity or violate policies might be rejected or removed from the Chrome Web Store.
You can learn more about today鈥檚 guidance in our Program Policies. These policy clarifications will go into effect on April 15, 2024. After that date, extensions in violation of these new policies may be removed from the Chrome Web Store and be disabled.
If you have any questions, you can contact developer support.
Thank you for your cooperation, and for your participation in the Chrome extension ecosystem!
The text was updated successfully, but these errors were encountered: