Commit 4e3ca1c2 authored by meacer@chromium.org's avatar meacer@chromium.org

Add Pepper flag to UMA plugin records.

BUG=285440

Review URL: https://chromiumcodereview.appspot.com/23534051

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222179 0039d316-1c4b-4281-b951-d872f2087c98
parent c571dd4b
......@@ -228,6 +228,7 @@ void SetPluginInfo(const content::WebPluginInfo& plugin_info,
plugin->set_name(UTF16ToUTF8(plugin_info.name));
plugin->set_filename(plugin_info.path.BaseName().AsUTF8Unsafe());
plugin->set_version(UTF16ToUTF8(plugin_info.version));
plugin->set_is_pepper(plugin_info.is_pepper_plugin());
if (plugin_prefs)
plugin->set_is_disabled(!plugin_prefs->IsPluginEnabled(plugin_info));
}
......
......@@ -319,6 +319,9 @@ message SystemProfileProto {
// If a client has multiple local Chrome user accounts, this is logged based
// on the first user account launched during the current session.
optional bool is_disabled = 4;
// True if the plugin is PPAPI.
optional bool is_pepper = 5;
}
repeated Plugin plugin = 7;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment