Does My Extension Violate the “Single Use” Policy?

[Developer]

I have a browser extension that replaces the new tab page.
Additionally, it uses declarativeNetRequest to modify URLs, such as upgrading HTTP to HTTPS or switching mobile versions to desktop.

Does this violate the “Single Use” policy compliance requirements?

[Oliver Dunk]

Hi,

I'd encourage you to look at the FAQ here: https://developer.chrome.com/docs/webstore/program-policies/quality-guidelines-faq#three

It's hard to answer this question in isolation as the purpose of the new tab page is unclear. If you are using multiple APIs, you need to make sure they are all related to a narrow focus area or subject matter. That is something which is very context dependent and will ultimately be determined at review time.

I'm sorry not to have a definite answer, but I hope that's helpful.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/8e7a14a3-5d8c-4f65-b358-437f1d899b43n%40chromium.org.

[Developer]

The new tab page serves as the user's bookmark hub, allowing them to add, delete, and modify bookmarks directly on the page.
In this case, the declarativeNetRequest API is used to automatically switch to a secure HTTPS connection if the user has saved a non-secure HTTP URL.

I am currently in the process of appealing [0-8558000038787], as I believe this feature does not constitute new functionality but rather enhances the existing functionality of the extension, specifically its quick access page.

In my understanding, a violation of the single-use policy would occur if I were providing a new tab page and, for example, also downloading music.

среда, 5 февраля 2025 г. в 15:30:33 UTC+4, Oliver Dunk:

[Oliver Dunk]

Ultimately, compliance with the single purpose policy is determined at review time.

I can't provide anything beyond what has already been said in the case I'm afraid. It is definitely not the case that it always makes sense for a new tab page extension to need the Declarative Net Request API, and the verdicts on your item seem reasonable to me.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB