ps: …but I still use Secunia for vulnerabilities. If it’s just for updates, and you run Firefox, the integrated checker is enough + Mozilla now dismisses plugins with serious vulnerabilities (like it happened with Java a little while ago). For all the rest, Secunia’s still the way to go.
So what, as in currently plug-ins aren’t checked when you do a check, that only covers add-ons not plug-ins. If you checked out the first link polonus gave it clearly states plug-ins aren’t currently checked. So we would have to wait for a firefox update that included plug-ins in this check.
so what, so this : (see screenshots), I’m already fine with the way it works, or is a click on find updates once in a while too hard ??? >>> there’s an check plugins updates button you see? no? and this button in the firefox interface leads to the page mentioned by Polonus, surprising no? ;D might not be an automatic check but that’s already something + they already have (as said) the ability to disable (through an update) an insecure plugin (done with Java a few weeks ago).
It stems from further back where you said/agreed that Firefox already checks for this:
That is what is being said, by default plug-ins aren’t checked on the auto updates function in firefox. This is I believe what Jahn was pointing out.
However as you point out, if you are aware that plug-ins ‘aren’t checked by the auto update’ then you could manually use the Find Updates in the Plug-ins section, for those that are blissfully unaware wouldn’t be aware they need to manually check.