We have faced a problem.
We can’t contribute our new add-on code because it is rejected during
check.
Checker notes that description is incorrect and it is a cause of
rejection.
Addon’s description does not match its function.
Addon is set to run on every page while its function only relates to
some pages which amounts to user tracking and adds unnecessary overhead.
Any tracking (e.g.
affiliate/referral/install/uninstall/upgrade/disable/error etc) to
outside sources requires clear disclosure in both the add-on
description and the Privacy Policy.
eg: content-script.js
We have corrected the description. Our add-on doesn’t gathering any tracking information, so Privacy Policyis empty, add-on flags has now “site-specific”-value
However it is still rejected due the description.
Where is the issue?
How can we correct the description to pass the check?
Since I was the one who reviewed that addon… here are some explanation:
1- Addon’s description does not match its function
Addon’s description: Enable screen sharing for flashphoner.com
Which means addon is meant for the domain of flashphoner.com
pageMod.PageMod({
include: "*", <-- this is the problem
include: "*", means addon is running on every page that user loads (not only flashphoner.com)
Why is addon running on HSBC bank site (for example) when its function relates only to flashphoner.com?
2- Tracking
Addon allows the target site (well, every site as it is now), to query visitor’s addon directly and covertly, to check if they have the addon installed or not and which domains they have enabled screen-sharing on. This is not only tracking the user by the target site but also has privacy issues. Websites should not be allowed to check visitor preferences without visitor’s consent.
Finally, addon can function normally and allow the user to share screen with flashphoner.com without the need for all above code.