we haven't updated the plugin-check page yet, it should be fully updated in a day or two.

There are some issues with the Tab mute feature in Flash that Adobe needs to address in a further update, so it could take longer than usual.

While the current version fis 20.0.0.235 as of December 8, I would not be be surprised if 20.0.0.238 or higher is released soon to fix a issue with tab mute as said.

I think it's less than ideal that the plugin check purports to show you if your plugins are up to date - to check in real-time against the actual current version of your plugins - when it doesn't actually do that.

I think it either needs to strive to do what it says it does, or, let the user know it doesn't necessarily do that.

For example, it could say "Up To Date* *actually maybe not up to date, you better go check with the vendor"

I guess there are reasons but I wonder why it doesn't work like I always assumed it did: that firefox would check against some API or web version number supplied by the plugin makers.

Might be less than ideal, but it keeps Firefox users from updating to a version that causes issues with Firefox. Like cor-el mentioned with the Tab Mute feature.

There is no API from the plugin vendors, this list is maintained by hand and we do the best we can, but sometimes it takes a day or two to update it. It's not meant to be a canonical list, but rather a resource for users.

Thanks for the information, I now have a better understanding of it.

EDIT: I would just like to say that my suggestion then, would be to add a 4th column to the plugin check page, which shows accurate up to date version info from the vendor. So everything would work the way it does now, which I understand it needs to due to compatibility issues and time/work factors, But, it would solve the information accuracy issue and empower users with that info and never have them thinking they are up to date when they aren't, which I think is a bad thing.

The 4th column would just be informational, so it doesn't have the compatibility or time issues of the rest of how plugin check works, ie: the new version would not need to be approved for that column. It could be fed by a scraper on a cron job or something, that just keeps checking the vendor web page.

I realize this would just be a nicety, an extra feature above and beyond what plugin check currently does. But I think it's a good idea and a worthwhile improvement, so I am mentioning it. Thanks