Closed Bug 1741908 Opened 3 years ago Closed 2 years ago

ensure abuse reports work with sitepermission addons

Categories

(WebExtensions :: General, task, P2)

task
Points:
2

Tracking

(firefox97 fixed)

RESOLVED FIXED
97 Branch
Tracking Status
firefox97 --- fixed

People

(Reporter: mixedpuppy, Assigned: rpl)

References

Details

(Whiteboard: [addons-jira])

Attachments

(5 files, 2 obsolete files)

No description provided.
Severity: -- → N/A
Assignee: nobody → lgreco
Status: NEW → ASSIGNED

TODO: to support abuse reports for the sitepermission addon type, we will have to:

  • [x] confirm if any of the abuse categories below should be hidden (e.g. like some are hidden for themes):
    • agreed to keep damage, broken, unwanted and other
  • [x] confirm if any of the existing strings associated to the abuse categories we will support have to be reworded (e.g. for themes some are)
    • some had to be reworded a little bit, see changes to the Fluent file in this patch.
  • [x] create new l10n entries for the '*-sitepermission' strings (like for themes and extension, see:
    https://searchfox.org/mozilla-central/search?q=-extension&path=abuseReports.ftl )
  • [x] confirm using addon.siteOrigin as the preferred support URL (included in the suggestion
    for the "broken" category, in the second screen after the category has been selected)
    • in the current version of this patch siteOrigin is going to be used as a fallback if no
      homepage_url or support url was explicitly specified
  • [ ] extend the existing tests to also cover the sitepermission addon type
    • [x] add a test case to cover all suggestions fluent strings
    • [ ] add one more test case to test the fallback to siteOrigin on no homepage_url in the manifest
    • [ ] make sure to cover also the fluent strings for the message bars (which also cover the completed submission)

Depends on D132396

Lets keep damage, broken, unwanted and other, all with the same wording. Wording can be tweaked in future versions (eg. next time we add a site permission).

reasons:

damage: some apis may provided access to system level resources
spam: the addon cannot insert stuff so hide it
settings: the addon cannot change settings, it only provides a permission for a given dom api, hide it
deceptive: on the fence, but since it can only provide a permission to a site, we'll hide it for now
broken: a user could perceive this is breaking something, so lets leave it visible
policy: the addon cannot contain anything, so hide this
unwanted: I don't see a reason to hide this even for themes, lets leave it visiable for site permissions
other: never hide

Attachment #9252914 - Attachment description: WIP: Bug 1741908 - Add support for abuse reporting to the sitepermission addon type. → Bug 1741908 - Add support for abuse reporting to the sitepermission addon type. r=mixedpuppy!
Points: --- → 2
Pushed by scaraveo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f9750807dbef
Move list of the addon types supported by the abuse reports into a single place. r=mixedpuppy
https://hg.mozilla.org/integration/autoland/rev/e5d02853985c
Add support for abuse reporting to the sitepermission addon type. r=mixedpuppy,fluent-reviewers
Regressions: 1729827
No longer regressions: 1729827
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
Pushed by flodolo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/28cffb1d6be7
pluralize string for site permissions abuse reporting r=flod,fluent-reviewers
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: