diff options
| author | bauerb@chromium.org <bauerb@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-02 09:31:11 +0000 |
|---|---|---|
| committer | bauerb@chromium.org <bauerb@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-02 09:31:11 +0000 |
| commit | 0a8b1e2c78db8b03065787c8b7b9d3fabb6729ee (patch) | |
| tree | 445be17ecbb9212c374c594b4a5ad80ef3954130 /chrome/chrome_tests.gypi | |
| parent | 796d0c6845a8eb6442e04035dc1b59d21555d7f3 (diff) | |
| download | chromium_src-0a8b1e2c78db8b03065787c8b7b9d3fabb6729ee.zip chromium_src-0a8b1e2c78db8b03065787c8b7b9d3fabb6729ee.tar.gz chromium_src-0a8b1e2c78db8b03065787c8b7b9d3fabb6729ee.tar.bz2 | |
Group plugins in about:plugins and show update link for out-of-date ones.
Re-landing patch by mavrommatis, original review here:
<http://codereview.chromium.org/1991005>
Original description follows:
(1) Group plugins with the same name together. (2) Show a download link for
plugin versions with known security problems in about:plugins.
BUG=3910,47858
TEST=Open "chrome://plugins", see that plugins are grouped, and that any vulnerable plugins are marked red. Try enabling and disabling plugin groups. Also, if the internal PDF plugin is enabled, it should stay enabled after a restart.
Review URL: http://codereview.chromium.org/2811037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51510 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
| -rw-r--r-- | chrome/chrome_tests.gypi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi index bfa6cec..b2174d3 100644 --- a/chrome/chrome_tests.gypi +++ b/chrome/chrome_tests.gypi @@ -898,7 +898,7 @@ 'browser/password_manager/password_store_default_unittest.cc', 'browser/password_manager/password_store_mac_unittest.cc', 'browser/password_manager/password_store_win_unittest.cc', - 'browser/password_manager/password_store_x_unittest.cc', + 'browser/plugin_updater_unittest.cc', 'browser/pref_member_unittest.cc', 'browser/pref_service_unittest.cc', 'browser/preferences_mock_mac.cc', @@ -1532,7 +1532,7 @@ 'browser/chromeos/options/wifi_config_view_browsertest.cc', 'browser/chromeos/panels/panel_browsertest.cc', 'browser/chromeos/status/clock_menu_button_browsertest.cc', - 'browser/chromeos/status/language_menu_button_browsertest.cc', + 'browser/chromeos/status/language_menu_button_browsertest.cc', 'browser/chromeos/status/power_menu_button_browsertest.cc', ], }], @@ -2465,7 +2465,7 @@ # If a test bundle is added to this coverage_build target it # necessarily means this file (chrome_tests.gypi) is changed, # so the action is run (coverage_bundles.py is generated). - # Exceptions to that rule are theoretically possible + # Exceptions to that rule are theoretically possible # (e.g. re-gyp with a GYP_DEFINES set). # Else it's the same list of bundles as last time. They are # built (since on the deps list) but the action may not run. |