Issue 3910: we should help users get the most up-to-date plug-ins
http://code.google.com/p/chromium/issues/detail?id=3910
Comment #3 by [EMAIL PROTECTED]:
This seems like it would be possible with an expansion of our existing
plugin list to
include the version number we're currently pointing to. (Or perhaps an
additional
file that has this data?) Any difference between the user's version and
our version
would prompt the info bar.
Maybe the logic could be:
- when a new plugin is instantiated,
- compare the version of the instantiated plugin against the version we
know about
in our download URL file
- if the version we know about is newer & the infobar hasn't been
recently shown,
- show the infobar with the plugin download URL
Complexity arises in the concept of "newer" plugins. i.e., How do we know
if version
"FOO" is newer or older than version "BAR"? If we make the assumption that
Chrome
always knows about the latest supported plugin version, any difference in
the two
means the user has an older version.
I'll need to do some research on if adding versions to our known plugin
download list
is possible, and how intensive it would be. I'll move this to the
appropriate
milestone thereafter.
Issue attribute updates:
Owner: [EMAIL PROTECTED]
Labels: -Mstone-1.0 Mstone-1.2
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
