My operating system is Centos 6.7, and browser that I use is Google chrome. While I go to most of the video sites, it gives me "couldn't load plugin" error (except youtube). I started wondering why is the error getting popped up, while I had already installed Adobe flash player and the version is 21.0.0.216. So, I decided to do some research on it to solve the issue. What I have understood is that there are two types of flash players, PPAPI and NPAPI, and for my system configuration, it needs NPAPI to be enabled, as given in this link (http://www.tweakjc.com/how-to-fix-chrome-couldnt-load-plug-in-error/#imageclose-113). But, unfortunate for me I don't have an option of NPAPI in my browser plugin list. screenshot of my AFP in the plugins list, where only PPAPI is available
Is there a way to get NPAPI type of AFP, or is my perception is right or is there any other workaround possible to play my vids? Thanks in advance
That link is to obsolete information; NPAPI support was completely removed from Chrome last year.
Related
When we want to integrate Google map in windows application by using C# it gives the following errors when we run the application
error : you seem to be using an unsupported browser
Based from this forum, it seems that there is/are one or more addons or extension which is not allowing map to load. You can try to check one by one. Maybe it updated and broke maps.
You can also check this SO question which states that maybe the WebBrowser control is emulating an older version of Internet Explorer on your machine.
By default, this feature is enabled for Windows Internet Explorer and for applications hosting the WebBrowser Control. To disable this feature by using the registry, add the name of your executable file to the following setting.
Hope this helps!
You can consider a different web browser embedded control. For example, you can look at Chromium Embedded Framework.
https://en.wikipedia.org/wiki/Chromium_Embedded_Framework
I believe it should work pretty well. According to the documentation this framework embeds a Chromium browser (open-source web browser closely related to the Google Chrome browser) which uses the modern HTML5 and V8 JavaScript engine.
Hello as you might now NPAPI is deprecated.
What are the alternatives to this? I see skype released now the web version where you need to install a web plugin to make voice and video calls. Looking over what I installed I arrived to the conclusion that on chrome they are using Google Native Client: https://developer.chrome.com/native-client
But this one is not supported on firefox/safari (only chrome).
On Firefox/Safary I'm not sure what they are using.
So what are now the best alternatives for this kind of job where using c++ is mandatory (to extend an existing app and make it available as web plugin)
Silviu
After Chrome drop the NPAPI support, there is no-common technology support by Firefox/Chrome/Safari. You can consider about Firebreath 2.0. It allow you use one C++ implement to support different browser.
It's not released yet... If you like to try version 2.0, you can get source code from https://github.org/firebreath/firebreath (the "refactor" branch)
Note: version 2.0 make huge change, because the call between plugin and javascript are asynchronous! Upgrade from older version required lots of javascript change.
I am developing my first extension for Chrome and as I am working on Ubuntu, I've encountered two awful bugs.
The first thing is that chrome.i18n.getUILanguage is not supported! (console gives me an error about unsupported method). The thing is that this problem is not listed on any WIKI page, which may become tricky for beginners. Anyone had similar issue? For now, I am using window.navigator.language.
The second bug is about rich notifications that are not supported (anyone knows when it will be released?). As far as I know, when the app will be about to send a notification, the scripts will stop due to the error (similar to the first bug). I am not sure if there is possibility to develop different packages for different platforms, but if I want my extension to be truly multi-platform, I will have to give up development of this feature.
Any suggestions or thoughts?
Thanks,
As i said earlier in a comment, it seems to be not supported with linux mint either where i'm developing the chrome extension.
In this link a member of the chrome team said that they submitted it... but this is not true.
Thanks for the window.navigator.language alternative.
I keep reading conflicting answers to this question, and I can't find a definitive answer in an official Google document.
By suppressing the blacklist I can enable hardware acceleration for almost every rendering feature under chrome://gpu-internals/ but not the 2D Canvas. My system is service pack 3, fully updated. DirectX 9. All drivers for the onboard video (Intel GMA3100) are completely up to date. The chip is quite capable, and I even flashed my mobo BIOS to the latest version as a last ditch effort. I'm thinking that Google just isn't supporting HW accel. for the 2D Canvas under Windows XP.
The problem is that Chrome developers have disabled Canvas HW Accel for XP, it calls Direct3DCreate9Ex from d3d9.dll which is DirectX 9L available only on Vista+, but it is possible to wrap D3D9Ex on Windows XP via WineD3D Direct3D to OpenGL wrapper. (special thanks to WineHQ/Crossover)
Then we need to disable blacklist and disable sandbox in launch options. (Special thanks to BlackWingCat)
I have already managed to force HW accel for Chromium-based browsers for Windows XP/2003. And it works somehow.
System requirements:
CPU with SSE3 feature support, OpenGL 3.0 hardware/software support.
In fact I use video card from "green" company :)
Installation:
1. Copy and paste d3d9.dll, wined3d.dll, libwine.dll into chrome folder where you have chrome.exe, for example "C:\Program Files\Google\Chrome\Application"
2. Copy and replace d3dcompiler_47.dll and libwine.dll into your Chrome folder where chrome.dll is, for example C:\Program Files\Google\Chrome\Application\49.0.2623.112.
3. Add launch parameters "--ignore-gpu-blacklist --no-sandbox --disable-infobars" to your Chrome shortcut. (without quotes)
4. Run Chrome with your modified shortcut
If you experience issues with Chrome after this hack you can just remove launch options from Chrome shortcut it will disable this hack.
Download:
ChromeHW_accel_XP.zip (tested with backported Chrome 50.0.2661.102 beta-m, Opera 37, Chrome 49)
Known issues:
1. Address bar flickers quickly when you type.
2. HTML5 video doesn't work correctly (you need to force to use Flash Player)
Actually, I can report that Opera 36/37 (chromium based) is a way more stable with this hw accel hack.
UPDATE:
New Chromium builds use libGLESv2.dll version 1.2.0.2448. I'm no expert in VB, but it seems as if the new version doesn't need the mod...
HOWEVER -
The new Chromium builds that use this new libGLESv2.dll always crash (And then restart automatically in safe mode) if you try to enable the overriding of GPU blacklist in flags.
If someone can check this out and report back it would be much appreciated (Could this have something to do possibly with the added support for DirectX 11?)
Update patch is released, anyone interested can check
My intention is to create a chrome plugin for the windows users. Is that possible to call windows api from Native Client /PPAPI. If possible how?
I am answering my question, as after some study, I found the answer from West a bit not right. I tried calling windows APIs in Pepper(PPAPI) Plugin and it works fine with a command line switch "--register-pepper-plugins" (not the --no-sandbox as specified by West). It seems safer to use this command line attribute as it is only registering a plugin in to the Chrome browser and not removing any sandbox. I thought of adding an answer after finding an actual pepper plugin existing in use, which uses the switch (the NetFlix pepper plugin for chromeos ).
Got more information to add. Chrome API is available which provides the multi-monitor information : chrome.systemInfo.display object provides all the necessary information. The chrome documentation is not updated. Important thing to note is that, the permission "systemInfo.display" is to be added in the manifest to use this object. Two bugs are reported in the functionality of this object.
1. The monitor name is same for all monitors "Generic PnP Monitor", the documentation claims to provide the user friendly name of monitors.
2. There is an event which should get invoked on resolution change of monitors, but the event is never getting invoked.
Currently the implementation is only for Windows OS. Support for other OS are on the way. Documentation says that the API is only available for Chrome App, but I haves tested that and the API is available on Chrome Extensions as well.
Unfortunately, the short answer is 'no'. Native Client is designed to be OS-independent and as safe as JavaScript. Think of Native Client as native code that has the same capabilities and restrictions as JavaScript. A Native Client module that made Windows API calls would break both of those design principles: it wouldn't run on, e.g., a Mac, and it would be a major security risk (imagine browsing to a web page that decides to erase files from your harddrive).
Since you mention Chrome, it may be interesting to you to know that web apps - whether they use JavaScript or Native Client - can request additional permissions as packaged apps in Chrome Web Store. However, native OS calls are still not possible for the reasons listed above.
NPAPI plugins do not have these restrictions, but the future of NPAPI, at least in Chrome, is uncertain (see the last paragraph of http://blog.chromium.org/2012/07/npapi-plug-ins-in-windows-8-metro-mode.html).
For development purposes, it is possible to turn Chrome's outer sandbox off with the command-line flag --no-sandbox and then run PPAPI plugins that make direct OS calls. This is meant for developers and is not a suitable option to be used by end-users.
If you could say a bit more about what you're trying to achieve, there may be ways to do this with Native Client/Pepper.