Enable pnacl by default

chrome/browser/ui/webui/nacl_ui.cc

Index: chrome/browser/ui/webui/nacl_ui.cc
diff --git a/chrome/browser/ui/webui/nacl_ui.cc b/chrome/browser/ui/webui/nacl_ui.cc
index 744d9cf99a4b2ea47329bcf8caa4eeb429defe87..324b5e4d939fd47f39903b9f80bfdfc82b9f1113 100644
--- a/chrome/browser/ui/webui/nacl_ui.cc
+++ b/chrome/browser/ui/webui/nacl_ui.cc
@@ -338,7 +338,7 @@ void NaClDomHandler::PopulatePageInformation(DictionaryValue* naclInfo) {
             pnacl_path.DirName().DirName().BaseName().LossyDisplayName());
   }
 
-  ListFlagStatus(list.get(), "Flag '--enable-pnacl'", switches::kEnablePnacl);
+  ListFlagStatus(list.get(), "Flag '--disable-pnacl'", switches::kDisablePnacl);

[jvoung (off chromium), 2013/07/18 17:01:00]

Might be more readable if this directly told the developer if PNaCl is enabled
or not, instead of saying if the "disable" flag was on or off. 

However, I suspect that if you want to say if PNaCl itself is enabled or not,
you also have to check if it's enabled in about:plugins also (not just this flag
from about:flags / the commandline).

You can customize this if you code it manually, instead of using ListFlagStatus.
We could get rid of that helper since it's only used in two places.

Actually, re: about:plugins -- the "Disable" link doesn't seem to work for
Native Client anymore.  Only works for other plugins.

[sehr, 2013/07/22 23:06:50]

Done.

   // naclInfo will take ownership of list, and clean it up on destruction.
   naclInfo->Set("naclInfo", list.release());
 }