bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Display info bar for vulnerable plugins

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
6 years ago
5 years ago

People

(Reporter: mcsmurf, Unassigned)

Tracking

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
I've noticed that Firefox does not display a info bar when a vulnerable plugin is used on a website (PluginVulnerableUpdatable event). I'm not sure if this is intended or not (from a UI point of view).
In contrast to that Firefox display a info bar for out-of-date plugins, see http://hg.mozilla.org/mozilla-central/annotate/cf1bbed46731/browser/base/content/browser-plugins.js#l674; you can also test this by reproducing the steps below with the Firefox 16.0.1 release, there the UI handles the Adobe Reader 10.0.1 plugin with a PluginOutdated event.

To test this:
1. Go to https://addons.mozilla.org/en-US/firefox/blocked/ and install a blocked software/plugin (I used Adobe Reader 10.0.1)
1.5. Select the Adobe Acrobat plugin under Applications in the preferences window (otherwise it will use pdf.js)
2. Visit http://plugindoc.mozdev.org/testpages/pdf.html
3. Observe that you get no info bar or any notification that this plugin is not up-to-date anymore. With the Firefox 16.0.1 you get a notification: "Some plugins used by this page are out of date."
(Reporter)

Comment 1

6 years ago
Looks like blocking the plugin (and forcing click-to-play instead) does actually work with this plugin, but it only works with a new profile. With my old profile blocking (click-to-play) does not work. I'm not sure what's wrong here. I suggest to keep this bug open, I'll morph the bug when I have more details what's going on here.
(Reporter)

Comment 2

6 years ago
Can't reproduce with my old profile anymore, resolving as wfm..
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.