Closed Bug 1863307 Opened 2 years ago Closed 2 years ago

Enable AMO hosted abuse report form on all channels for Firefox Desktop builds

Categories

(Toolkit :: Add-ons Manager, task, P1)

task

Tracking

()

VERIFIED FIXED
122 Branch
Tracking Status
firefox121 --- verified
firefox122 --- verified

People

(Reporter: rpl, Assigned: rpl)

References

Details

(Whiteboard: [addons-jira])

Attachments

(2 files)

As a separate followup to Bug 1859791, we will be setting the new about:config pref "extensions.abuseReport.amoFormEnabled" to true by default on all channels for Firefox Desktop builds.

The AMO hosted form is still being completed, but the goal is to be setting "extensions.abuseReport.amoFormEnabled" to true by default before the end of the Firefox 121 Nightly or Beta cycle.

Whiteboard: [addons-jira]
Assignee: nobody → lgreco
Status: NEW → ASSIGNED
Severity: -- → N/A
Priority: -- → P1
Depends on: 1865840
Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/8126bc040321 Enable AMO hosted abuse report form on all channels for Firefox Desktop builds. r=willdurand

Backed out for causing bc failures in browser_ext_browserAction_contextMenu.js

And also this: https://treeherder.mozilla.org/logviewer?job_id=437591865&repo=autoland

Flags: needinfo?(lgreco)

Working on it, that test also need to be updated to account for the amo form url to be opened when the pref is true (and the pref that includes the url to the form to be set to be pointed to a local address, so that we would not hit a non-local address failure while running the test).

Apologies for missing to notice this additional test before the push to autoland.

Flags: needinfo?(lgreco)
Depends on: 1866565
Backout by imoraru@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8a861d9d1b4a Backed out changeset 8126bc040321 for causing crashes in /browser_ext_browserAction_contextMenu.js CLOSED TREE

Push to try with both the attached patches applied (the one already attached and the new parent one added in comment 6 to adapt those two additional mochitest-browser tests):

Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/6d16060ff7ea Adapt mochitest-browser tests covering the report context menu item to run with amoFormEnabled true/false. r=willdurand https://hg.mozilla.org/integration/autoland/rev/2ffce169bf66 Enable AMO hosted abuse report form on all channels for Firefox Desktop builds. r=willdurand
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch

Verified as Fixed. Tested on the latest Nightly (122.0a1/20231128094907) under Windows 10 x64, Ubuntu 22.04 LTS and macOS 11.3.1.

The new abuse report AMO form is now enabled by default as a result of the extensions.abuseReport.amoFormEnabled pref being set to true from the start.

Tested using extensions.abuseReport.amoFormURL set to -DEV (https://addons-dev.allizom.org/%LOCALE%/%APP%/feedback/addon/%addonID%/).

Reporting add-ons from all available locations in Firefox (three-dot menu on add-on card, three-dot menu from the add-on detail view, extensions panel context menu, extensions panel gear menu, context menu when pinned to toolbar and pageAction) and reporting installed add-ons from their AMO detail page will now open the new report abuse AMO form.

The abuse report form URL correctly matches the format set through extensions.abuseReport.amoFormURL i.e. https://addons.mozilla.org/<locale>/<application>/feedback/addon/<guid>/

The request payload also contains the correct information upon submitting the report. For example:

{
"addon": "arabicoffee@dictionaries.addons.mozilla.org",
"addon_version": "3.2.20120321.1webext",
"location": "addon",
"message": "test",
"reason": "feedback_spam",
"reporter_email": "asfd",
"reporter_name": "asdf"
}

Considering the above, the issue is Fixed.

Status: RESOLVED → VERIFIED

Comment on attachment 9362109 [details]
Bug 1863307 - Enable AMO hosted abuse report form on all channels for Firefox Desktop builds. r?willdurand!

Beta/Release Uplift Approval Request

  • User impact if declined: The abuse report form available to the users in Firefox 121 would still be the same one integrated in older Firefox versions, which is not going to be compliant to DSA (EU Digital Services Act) requirements, while the one hosted on addos.mozilla.org and enabled by default by this patch is going to be DSA compliant.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: Same as the QA test plan used to verify this feature on Nightly.
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This feature has been explicitly QA verified on nightly and beta, and it is covered by automated tests. These two patches are only including the final pref flipping and tweaks to the automated tests (to cover the expected behavior of the abuse reporting feature with amoFormEnabled pref set to both true and false).
  • String changes made/needed:
  • Is Android affected?: No
Attachment #9362109 - Flags: approval-mozilla-beta?
Attachment #9365502 - Flags: approval-mozilla-beta?

Comment on attachment 9362109 [details]
Bug 1863307 - Enable AMO hosted abuse report form on all channels for Firefox Desktop builds. r?willdurand!

Approved for 121.0b5.

Attachment #9362109 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9365502 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Verified as Fixed. Tested on Beta Developer Edition 121.0b6 (121.0b6/20231201091738) and on the latest Beta Developer Edition (121.0b7/20231204092159) under Windows 10 x64, Ubuntu 22.04 LTS and macOS 11.3.1.

Beta Developer Edition has been used due the need to change several prefs to be able to install add-ons from -DEV.

The new abuse report AMO form is now enabled by default as a result of the extensions.abuseReport.amoFormEnabled pref being set to true from the start.

Tested using extensions.abuseReport.amoFormURL set to -DEV (https://addons-dev.allizom.org/%LOCALE%/%APP%/feedback/addon/%addonID%/).

Reporting add-ons from all available locations in Firefox (three-dot menu on add-on card, three-dot menu from the add-on detail view, extensions panel context menu, extensions panel gear menu, context menu when pinned to toolbar and pageAction) and reporting installed add-ons from their AMO detail page will now open the new report abuse AMO form.

The abuse report form URL correctly matches the format set through extensions.abuseReport.amoFormURL i.e. https://addons.mozilla.org/<locale>/<application>/feedback/addon/<guid>/

The request payload also contains the correct information upon submitting the report. For example:

{
"addon": "arabicoffee@dictionaries.addons.mozilla.org",
"addon_version": "3.2.20120321.1webext",
"location": "addon",
"message": "test",
"reason": "feedback_spam",
"reporter_email": "asfd",
"reporter_name": "asdf"
}

Considering the above, the issue is Fixed on Beta as well.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: