Hi folks!
I am in the process of updating our extension from v2 to v3 and have some questions about policy compliance.
Our extension works by capturing the URL of the current page when the user clicks the extension button. We intend to use an iframe (or something similiar) within the extension popup to display edit details and confirmation screens hosted as HTMX pages on our site.
After reviewing the policies at
https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements, I am a little concerned about potential violations, particularly regarding the transparency of the extension’s functionality.
* Does wrapping confirmation pages et al from our site in an iframe or something in an extension popup violate Chrome Web Store Manifest v3 policies (like being able to determine full functionality of the extension)?
The primary function of our extension seems straightforward — adding the current URL to a user’s account on our service. However, I want to check our approach aligns with the latest policies before proceeding further.
I appreciate any guidance or clarification folks can provide.
Thanks, everyone!
Adam Wolf