Using cef_binary_3.1180.719_windows, if I direct my web browser to my own Native Client application on an HTTP server I stared, I get "Couldn't load plug-in" in the <embed> tag.

What steps will reproduce the problem? 1. Install Native Client SDK: https://developers.google.com/native-client/sdk/ 2. Start web server with demo applications 3. Browse to local server with cefclient, and it cannot load the plugin.

Also, if you look at the 'Plugin Info' page in cefclient, many plugins are listed but not Native Client; compare this with regular chrome 'about://flags', which does say there is a Native Client plugin installed.

What is the expected output? What do you see instead?

Expected: Native client plugin loading successfully.

Seen: error loading plugin.

What version of the product are you using? On what operating system?

cef_binary_3.1180.719_windows

Please provide any additional information below.

Comment deleted

I got a Error that can't load flash plug-in,and got "Couldn't load plug-in" in the tag.

then i used function "CefAddWebPluginPath" and 'CefRefreshWebPlugins' to add flash plug-in.but not take affect.

how to manual add a plug-in?

Any update on this issue? I'm getting "Browser does not support NaCl (newlib), or NaCl is disabled" when running the getting started part2 in cef, while it works in chrome. I also confirm the plugin is not present in the 'Plugin Info' page.

Command line call ./cefclient --no-sandbox --disable-web-security --enable-nacl

OS: Ubuntu 12.04 32-bit CEF: cef binary 3.1750.1638 linux32 client

I just encountered the lack of NaCl support in cef binary 3.1916.1701 as well. Also confirming that the Native Client (ppGoogleNaClPluginChrome.dll PPAPI in-process) plugin shown in Chrome (34) does not appear on the cefclient plugin page, although all other plugins match.

I couldn't locate flags for enabling it in the cef *.gyp flags - can it be enabled?

OS: Windows 7 64-bit CEF: cef binary 3.1916.1701 windows32

Adding NaCl support will require code changes in CEF. Usage of the "DISABLE_NACL" macro in src/chrome can provide rough guidance on the necessary changes: https://code.google.com/p/chromium/codesearch#search/&q=DISABLE_NACL%20src/chrome&sq=package:chromium&type=cs. Note that in-process and out-of-process plugin loading uses different code paths (see related comments on issue #1331).

Any more progress on this?

CEF is transitioning from Google Code to Bitbucket project hosting. If you would like to continue receiving notifications on this issue please add yourself as a Watcher at the new location: https://bitbucket.org/chromiumembedded/cef/issue/705