Comment #1 on issue 29719 by luke.hutch: Extensions need source-based trust verification mechanism http://code.google.com/p/chromium/issues/detail?id=29719
Source and resources of *installed* extensions should also be viewable in the browser from the right-click menu of extensions, so if someone suspects the extension is doing something malicious, they can quickly do a visual check. This will also help developers quickly learn to write better extensions by being able to look at other people's work. (Separate issue: Hopefully the javascript is not too obfuscated e.g. by GWT -- maybe hooks for a javascript de-obfuscator can be added to the source view?) See also Issue 30781 that talks about how *good* an extension is (this issue talks about rating how *trusted* an extension is). -- 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 -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
