diff options
| author | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-29 23:14:46 +0000 |
|---|---|---|
| committer | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-29 23:14:46 +0000 |
| commit | fbf3714a8a46a52a95501aeaa73300b12bdfbae1 (patch) | |
| tree | ef0c750c7c4c626a6051626098d7aa40c096c390 /chrome/chrome_tests.gypi | |
| parent | 99bb53e5bed242585c66c3903d5df7d5a06560b4 (diff) | |
| download | chromium_src-fbf3714a8a46a52a95501aeaa73300b12bdfbae1.zip chromium_src-fbf3714a8a46a52a95501aeaa73300b12bdfbae1.tar.gz chromium_src-fbf3714a8a46a52a95501aeaa73300b12bdfbae1.tar.bz2 | |
Revert 51110 because of regression 47858- Group plugins in about:plugins and show update link for out-of-date ones.
Tracking 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
TEST=Open "chrome://plugins", see that plugins are grouped, and that any vulnerable plugins are marked red. Try enabling and disabling plugin groups.
Review URL: http://codereview.chromium.org/2835018
TBR=bauerb@chromium.org
Review URL: http://codereview.chromium.org/2805048
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51191 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 d055b35..e956ce6 100644 --- a/chrome/chrome_tests.gypi +++ b/chrome/chrome_tests.gypi @@ -897,7 +897,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/plugin_updater_unittest.cc', + 'browser/password_manager/password_store_x_unittest.cc', 'browser/pref_member_unittest.cc', 'browser/pref_service_unittest.cc', 'browser/preferences_mock_mac.cc', @@ -1522,7 +1522,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', ], }], @@ -2487,7 +2487,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. |