Extension Block Request: Misleading or deceptive add-ons
Categories
(Toolkit :: Blocklist Policy Requests, task)
Tracking
()
People
(Reporter: aliceg-85, Assigned: Fallen)
Details
Extension name | Misleading or deceptive add-ons |
Extension versions affected | <all versions> |
Platforms affected | <all platforms> |
Block severity | hard |
Reason
These add-ons violate No Surprises policy by having a general search functionality in the new tab page in the add-on. The names suggest (MyFormsFinder,FreeTemplateFinder,RecipeSearch) the main functionality is to search for (forms,templates,resipces). The install flows don't offer disclosure and are deceptive.
Extension IDs
_flMembersttab03_@free.myformsfinder.com
_ejMembersttab03_@free.downloadrecipesearch.com
_psMembersttab03_@www.freetemplatefinder.com
Updated•4 years ago
|
Just checking in on this one, is there any update yet?
Assignee | ||
Comment 2•4 years ago
|
||
I've reviewed the add-ons and confirm that they are violating our no surprises and data consent policies.
Assignee | ||
Comment 3•4 years ago
|
||
The block has been staged. Simon, can you review and push?
Comment 4•4 years ago
|
||
Done.
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
We are making some changes to this block. Jorge, can you review and push?
Comment 6•4 years ago
|
||
The block update is live on Kinto. I think we need to make the same change on the AMO side, but I'm not quite sure about this, so I'm keeping this open.
Comment 7•4 years ago
•
|
||
(In reply to Philipp Kewisch [:Fallen] [:📆][:🧩] from comment #5)
We are making some changes to this block. Jorge, can you review and push?
Can you document what the changes were in this bug so the changes on AMO can be verified? Having checked with Andrew, any changes are automatically handled.
Assignee | ||
Comment 8•4 years ago
|
||
The block should be changed to a partial block from 0 - 8.*. I also changed the description of the block slightly to add info that users should upgrade to 9 or later.
Comment 9•4 years ago
|
||
The developer was able to submit new versions of the extension and get them signed, so it looks like the AMO side was covered automatically, which was also confirmed on Slack.
Description
•