diff options
| author | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-06 21:05:21 +0000 |
|---|---|---|
| committer | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-06 21:05:21 +0000 |
| commit | 136564ee7820c466a55a97454389ed9c3bdcab65 (patch) | |
| tree | 97c9227e6da946b8f864d3f2ce66d190b3c3909a /webkit/tools/layout_tests/test_expectations.txt | |
| parent | c35c5e5f0a6d50f184759419c418b198f989ce72 (diff) | |
| download | chromium_src-136564ee7820c466a55a97454389ed9c3bdcab65.zip chromium_src-136564ee7820c466a55a97454389ed9c3bdcab65.tar.gz chromium_src-136564ee7820c466a55a97454389ed9c3bdcab65.tar.bz2 | |
Switch extension update manifest parse errors to LOG(WARN).
Before this patch they are using ExtensionErrorReporter, but I
don't think it's actually useful for users to see them on the
chrome://extensions page.
BUG=http://crbug.com/18565
TEST=You should no longer see messages like "Extension update
manifest parse error: Invalid codebase url"on the
chrome://extensions page.
Review URL: http://codereview.chromium.org/164008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22662 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/tools/layout_tests/test_expectations.txt')
0 files changed, 0 insertions, 0 deletions