Closed Bug 1556299 Opened 6 years ago Closed 6 years ago

A real prevention of bug 1548973

Categories

(Toolkit :: Add-ons Manager, defect)

60 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: u20230201, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Steps to reproduce:

I was affected by bug 1548973.

Actual results:

The bug was closed, bu tit's unclear what had been done to prevent it from happening again. Comments on bug 1548973 are not allowed, so I had to star ta new one.
Bug 1548973 caused Firefox to disable all pluigins while running without asking the user what to do.

Expected results:

In case some plugin cannot be verified any more in the future, Firefox should display a message like this (salt and pepper added):
"Your plugin {plugin} could not be verified any more due to {reason}. Should your plugin be disabled as we did last time, possibly harming your security and/or privacy, or would you like to continue using {plugin} despite of this problem?" ({xxx} are obvious placeholders.)

Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit

The priority flag is not set for this bug.
:ddurst, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ddurst)

This is not an actionable bug.

The repercussions of 1548973 are pretty clear to Mozilla writ large. This is not a single thing that can be solved as a bug. As there is an internal review of everything about this ongoing, I'm closing this report in favor of whatever solution the internal review demands.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(ddurst)
Resolution: --- → INVALID

(In reply to David Durst [:ddurst] from comment #2)

This is not an actionable bug.
Actually I think it is: In the past all plugins suddenly were disabled without a proper reason being given AND without asking the user for a choice whether to disable all the plugins, or to continue using them.
So nothing is to be done as a consequence?

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