Comment 110 for bug 538796

Revision history for this message
In , Jst (jst) wrote :

The UX for blocking depends on what level of blocking we do for a given plugin. There's two levels we can choose from, soft and hard, in the case of a soft block the user will receive a notification about a plugin (or extension) being blocked, saying that there are known issues with the plugin in question but the user can choose to enable the plugin at their own risk. In the case of a hard block, the same thing applies except that there's no option for the user to enable the plugin any more.

The notification that is shown also contains a link to a webpage with more information, but it's a generic page for all plugins. But we can of course add to that page so that there's information specific to whatever plugins are blocked etc.

These notifications comes typically ~10 minutes after firefox was launched, or at a seemingly random point after that (I believe we check once a day) if the users instance of Firefox had already done its initial block list check when the plugin block went into effect.