Blocklist UI must be more intelligent when asking for a restart

RESOLVED WONTFIX

Status

()

Toolkit
Add-ons Manager
RESOLVED WONTFIX
5 years ago
3 months ago

People

(Reporter: sachin, Unassigned)

Tracking

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
When an installed extension is detected as blocklisted after a blocklist update, a blocklist UI is shown. The blocklist UI contains two buttons "Restart Now" and "Restart Later".

If it is a hard block the add-on get disabled automatically. If a restart is not needed the user doesn't have to do anything. The restart buttons must be hidden.

If it is a soft block the user may choose to not to disable the add-on in which case also the restart buttons must be hidden.

Perhaps an "OK" button must be shown instead?

Cases of both hard and soft blocks and multiple add-ons would have to be dealt with similarly.
(In reply to Sachin Hosmani [:sachin] from comment #0)
> When an installed extension is detected as blocklisted after a blocklist
> update, a blocklist UI is shown. The blocklist UI contains two buttons
> "Restart Now" and "Restart Later".
> 
> If it is a hard block the add-on get disabled automatically. If a restart is
> not needed the user doesn't have to do anything. The restart buttons must be
> hidden.

A restart is always needed in this case
(In reply to Dave Townsend (:Mossop) from comment #1)
[...]
> A restart is always needed in this case

Even for a restartless extension?
(In reply to Tony Mechelynck [:tonymec] from comment #2)
> (In reply to Dave Townsend (:Mossop) from comment #1)
> [...]
> > A restart is always needed in this case
> 
> Even for a restartless extension?

Disabling a restartless extension at runtime requires that we trust that the extension properly unloads and cleans up after itself. If an extension is known to be malicious or unstable then we can't trust it to do that, so yes even for a restartless extension we need to restart to be sure we've got rid of it.
(Reporter)

Comment 4

5 years ago
So this bug would apply to only the other case I mentioned. The case when the UI consists of only softblocks and the user decides not to block any of them. I think a "Close" button would make sense there.

I could take this bug if we want it fixed.
Non-restartless extnesions and legacy extensions are no longer supported, which makes this irrelevant
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.