Closed Bug 912815 Opened 12 years ago Closed 7 years ago

Expose SelfSupport API to about:healthreport iframe to disable add-ons

Categories

(Firefox Health Report Graveyard :: Client: Desktop, defect, P4)

Product:
Firefox Health Report Graveyard
Component:
Client: Desktop
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: gps, Unassigned)

Details

(Whiteboard: [measurement:client])

Coming out of the stability work week was the desire to have FHR disable add-ons that are bad. The UX would be something like: 1) User goes to about:healthreport 2) iframe does its thing (we don't care what - it's an iframe!) and somehow determines that AddonX is "bad." 3) User is somehow prompted that AddonX is "bad" and is offered a simple way to disable it. 4) iframe sends a message back to chrome which then proceeds to disable AddonX. I raised the security concerns of this proposal at https://groups.google.com/forum/#!topic/mozilla.dev.security/1pNTVJQPxMs and it appears to have tentative support. I guess the next step is to get more technical.
Whiteboard: [StabilityWeek2013]
Priority: P2 → P4
Summary: Expose API to about:healthreport iframe to disable add-ons → Expose SelfSupport API to about:healthreport iframe to disable add-ons
Whiteboard: [StabilityWeek2013] → [measurement:client]
See https://bugzilla.mozilla.org/show_bug.cgi?id=1497137; component has been deprecated.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.