Extension Rejected Reason is Unclear

[Norton Extensions for Google Chrome]

Hi

I'm working for Norton Family team and we have our Norton Family extension published in chrome webstore for many years now.

https://chrome.google.com/webstore/detail/norton-family/napjheenlliimoedooldaalpjfidlidp

In our recent update, our extension (published on 28th Feb 2020) got rejected stating that it violates the "Use of Permissions" section of the policy.

We have requested for detailed information on why it was rejected, but until now we haven't got the real reason for rejection and every time we get the same template response from chrome webstore team.

All those response have one thing in common is about History permission. Here is some variation of response through the template email.

1. Don't request permission which are not used such as History.  
2. Example : chrome.history
3. Example :History

We have already explained that we are using history permission and it is used to go back to the previous page from Norton Family block page.

Even after providing all the details, we still get the same template response. 

Posting here in this forum to get more descriptive reason for rejection and mitigation required to resolve this issue.

Any help on this is much appreciated.

Here is the reference to the script that is using history permission (this script is part of the extension)

FileName: ..\RedirectPages\RedirectPages.js

chrome-extension://napjheenlliimoedooldaalpjfidlidp/RedirectPages/RedirectPages.js

 

function handleRedirect(mode) {

…

history.back();

…

}

Regards

Suyambu

[Simeon Vincent]

Hey Suyambu,

This extension is requesting but not using the history permission. history.back() is an open web API and does not require permissions to use. chrome.history is an extensions-only API that requires the history permission.

Cheers,

Simeon - @dotproto

Extensions Developer Advocate

--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ef486047-ec6a-4f9e-b95a-fc4b7aaa62d0%40chromium.org.

[Norton Extensions for Google Chrome]

Thanks for the quick reply Simeon, i'll check this and get back if there are any further clarifications.

- Suyambu

On Friday, April 3, 2020 at 4:31:04 AM UTC+5:30, Simeon Vincent wrote:

Hey Suyambu,

This extension is requesting but not using the history permission. history.back() is an open web API and does not require permissions to use. chrome.history is an extensions-only API that requires the history permission.

Cheers,

Simeon - @dotproto

Extensions Developer Advocate

Hi

I'm working for Norton Family team and we have our Norton Family extension published in chrome webstore for many years now.

https://chrome.google.com/webstore/detail/norton-family/napjheenlliimoedooldaalpjfidlidp

In our recent update, our extension (published on 28th Feb 2020) got rejected stating that it violates the "Use of Permissions" section of the policy.

We have requested for detailed information on why it was rejected, but until now we haven't got the real reason for rejection and every time we get the same template response from chrome webstore team.

All those response have one thing in common is about History permission. Here is some variation of response through the template email.

1. Don't request permission which are not used such as History.  
2. Example : chrome.history
3. Example :History

We have already explained that we are using history permission and it is used to go back to the previous page from Norton Family block page.

Even after providing all the details, we still get the same template response. 

Posting here in this forum to get more descriptive reason for rejection and mitigation required to resolve this issue.

Any help on this is much appreciated.

Here is the reference to the script that is using history permission (this script is part of the extension)

FileName: ..\RedirectPages\RedirectPages.js

chrome-extension://napjheenlliimoedooldaalpjfidlidp/RedirectPages/RedirectPages.js

 

function handleRedirect(mode) {

…

history.back();

…

}

Regards

Suyambu

--