Closed Bug 1614653 Opened 5 years ago Closed 5 years ago

Remove the extensions.abuseReports.openDialog pref and the related implementation and XUL elements from about:addons

Categories

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

task

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox78 --- fixed

People

(Reporter: rpl, Assigned: rpl)

References

Details

Attachments

(3 files)

As part of Bug 1580554, we implemented a new dialog mode for the abuse report panel, initially used for the abuse reports triggered from AMO, and then also for the reports triggered from about:addons and the rest of the Firefox UI (starting from Firefox 73, Bug 1598079).

We remove the "extensions.abuseReports.openDialog" pref and the related code and XUL elements from the about:addons internals (e.g. a couple of nightly cycles after the "report panel in dialog mode" has reached release).

Priority: -- → P3
See Also: → 1598079, 1580554
Assignee: nobody → lgreco
Status: NEW → ASSIGNED
Priority: P3 → P1
Attachment #9141793 - Attachment description: Bug 1614653 - Move into browser_html_abuse_report_dialog.js all test tasks previously shared by multiple test files. r?mstriemer! → Bug 1614653 - Move into browser_html_abuse_report.js all test tasks previously shared by multiple test files. r?mstriemer!

I think that the bug should be fixed by now because it blocks bug 1525179. It's the last thing still in the XUL page other than the browser for the HTML document.

Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/92e149d41267 Remove the extensions.abuseReports.openDialog pref and the related implementation and XUL elements from about:addons. r=mstriemer,fluent-reviewers,flod https://hg.mozilla.org/integration/autoland/rev/682318515715 Move into browser_html_abuse_report.js all test tasks previously shared by multiple test files. r=mstriemer https://hg.mozilla.org/integration/autoland/rev/d3971308b443 Remove abuse-report-frame.js and move openAbuseReport into extensions.js. r=mstriemer
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78

Can this be uplifted to Beta?

Firefox Beta Uplift Request

Risk: Low because it only has an effect with the openDialog pref set to false

(In reply to Nicohumor from comment #7)

Can this be uplifted to Beta?

No. The risk may be low, but there is no real value for the user by uplifting this to beta, and so in my opinion it isn't something to uplift.

If Bug 1525179 is the reason why you think we should uplift this, then take into account that uplifting this wouldn't help with that neither:
Even if this was in 77 (even landed there, instead of being uplifted) it would not make it easier to get Bug 1525179 in 77, Bug 1525179 is a bigger (and more likely risky) change and I'm pretty sure that an uplift request for it would not be created nor accepted.

(In reply to Luca Greco [:rpl] [:luca] [:lgreco] from comment #9)

(In reply to Nicohumor from comment #7)

Can this be uplifted to Beta?

No. The risk may be low, but there is no real value for the user by uplifting this to beta, and so in my opinion it isn't something to uplift.

If Bug 1525179 is the reason why you think we should uplift this, then take into account that uplifting this wouldn't help with that neither:
Even if this was in 77 (even landed there, instead of being uplifted) it would not make it easier to get Bug 1525179 in 77, Bug 1525179 is a bigger (and more likely risky) change and I'm pretty sure that an uplift request for it would not be created nor accepted.

OK.

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

Attachment

General

Created:
Updated:
Size: