Pepper: Remove trusted plugin loadable module.

chrome/common/chrome_paths.cc

Index: chrome/common/chrome_paths.cc
diff --git a/chrome/common/chrome_paths.cc b/chrome/common/chrome_paths.cc
index 6960bf3c61e3bd02a701c4c3d91821208cfcf337..ad64d2fb0b7a34c05a54cbe21df1216fdd3509fc 100644
--- a/chrome/common/chrome_paths.cc
+++ b/chrome/common/chrome_paths.cc
@@ -59,7 +59,10 @@ const base::FilePath::CharType kInternalPDFPluginFileName[] =
     FILE_PATH_LITERAL("libpdf.so");
 #endif
 
-// File name of the internal NaCl plugin on different platforms.
+// Historical file name of the internal NaCl plugin on different platforms.
+// TODO(teravest): See if we can change the strings here to not be an explicit
+// filename. I've left this as the historical value in case disabled-plugin
+// information is stored relative to file path.

[dmichael (off chromium), 2014/07/18 18:08:37]

Hmm, chromoting seems to use a special string:
internal-remoting-viewer

It might be good to follow up to find out if your suspicion is right. If so, I
think I agree with leaving it alone until the plugin is all-the-way gone. Then
we're left with the somewhat strange question of what to do (if anything) for
users who had the plugin disabled. Probably we accept that some users will be
affected, but that they still have enough control since they can separately
disable PNaCl.

[teravest, 2014/07/28 18:40:08]

Done.

 const base::FilePath::CharType kInternalNaClPluginFileName[] =
 #if defined(OS_WIN)
     FILE_PATH_LITERAL("ppGoogleNaClPluginChrome.dll");