NPAPI plugins are not supported on Microsoft's new browser Edge.
Google Chrome developed Chrome Native Messaging in order to interact with an executable installed on the computer provided its link on the registry (for Windows OS).
Firefox seems to want to support Chrome extensions in the future, and we can assume the browser will eventually support Chrome Native Messaging as well.
Internet Explorer will continue to support NPAPI until 2020 (from what I heard).
For Edge, no solution has yet been developed (or is there one?)
I'm willing to work with URL handlers (myapplication://mydata) in order to compensate for this lack. Is there a better approach so far?
https://msdn.microsoft.com/en-us/library/aa767914%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
My intent is to communicate through an HSM installed on the computer, and use the Crypto API interface, or a PKCS#11 driver in order to sign data and send back the result to the browser. With a chrome native messaging extension, it actually works well. With a URL Handler, I will be able to send data to the executable, but I won't get the result, so I will have to think to post the result to a web specific URL, but this can result in a security hole to my perspective.
Thanks in advance,
EDIT : 2017-01-14 : The following link shows the progress of the adaptation of the Microsoft Edge Extension API :
https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/api-support/extension-api-roadmap/
EDIT: as Beckyang posted recently, there is a link where you can vote for the feature to be developed in priority, here :
https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/13612338-native-messaging
After reading some recent news:
https://github.com/david-sabata/web-scrobbler/issues/678
http://www.theverge.com/2015/7/30/9072271/microsoft-windows-10-updates
http://news.softpedia.com/news/microsoft-wants-google-chrome-extensions-to-work-on-edge-with-zero-work-to-do-488282.shtml
It seems like the adaptation of the initial Chrome extension will be possible as soon as Microsoft has implemented a "Chrome-Extension-like" API. So, eventually, It won't be necessary to develop something completely new.
The Native APIs are supported in Windows 10 Insider Preview Build 15002.
Native messaging in Microsoft Edge.
Related
We have recently enrolled onto Chrome's origin trial for the new WebCodecs API (formerly known as "MediaCodecs"). The origin trial is supposed to start in Chrome 86 (see https://www.chromestatus.com/features/5669293909868544).
Despite that, the corresponding Web APIs (eg., VideoDecoder) are not available in the Chrome beta (version 86) and development (version 87) releases. Does anyone know Google's policy as to when features behind an origin trial are actually made available to developers?
OK, found it. The WebCodecs API does not (yet?) appear under chrome://flags. However, it can be enabled when invoking Chrome on the command line (Chrome 86+ only). So on Linux, this is:
google-chrome-beta --enable-blink-features=WebCodecs
Other than that, when putting a site under the respective origin trial, the WebCodecs APIs (eg., VideoDecoder) are also automatically exposed.
According to https://www.chromestatus.com/features/schedule it's supposed to come to chrome 86 stable on October 19.
Chrome 88 can work out of box now :-)
An example:
WebCodecs MP4 extraction demo
I am developing a website which requires camera and microphone for communication.
The site uses Twilio communication for audio/video calls.
Twilio device setup is failing and is giving an error as:
Twilio.Exception: twilio.js 1.3+ SDKs require WebRTC/ORTC browser support. For more information, see https://www.twilio.com/docs/api/client/twilio-js. If you have any questions about this announcement, please contact Twilio Support at .
To which I tried to debug and found that for my website in Google settings, microphone, camera and location settings are set to Block and is Disabled.
I have tried,
Resetting the Chrome browser
Upgrading to latest version of Chrome
Re-installing the Browser
But to no success.
This is how the chrome settings looks like:
Note: This seems to happening on 2 of my laptops, although on some machines it is working properly and the settings to these items is Allow in those machines. I have a customer demo and will have to use my laptop for it.
Any help is highly appreciated!
The getUserMedia API which allows access to the camera and microphone requires a secure context, i.e. https. See this blog post for background information. Recent versions of Chrome do not make getUserMedia available on http anymore.
Switch to https which should work out of the box on Heroku.
I need to develop some sort of browser plugin/extension to track search string on some search engine web site, ex: google.com, bing.com.
From the research, for chrome extension, I saw somebody suggest content js is the way to go. Is it true? Is there a cross-browser approach?
You can use Content.JS or any other JS library you like for developing an extension but with only JS library you cannot develop an extension.
There is a specific way for each browser. It contains at least 4 files.
(1) Manifest file (2) HTML file (3) JS file (4) CSS file
You also need to refer browsers object model.
You can refer links below may help you to get more information.
(1) Creating a Microsoft Edge extension
(2) Getting Started Tutorial to create an extension for Chrome
(3) Your first extension for FireFox
To support cross browser functionality, You can try to port your chrome extension to Firefox or MS Edge. To get more information on porting an extension, you can refer links below.
(1) Porting an extension from Chrome to Microsoft Edge
(2) Porting a Google Chrome extension
Note:- You also need to refer policy of each browser to access browsing data of users. It can be possible that all browser has some difference in their policies.
I've seen conflicting and stale information regarding whether Postman Chrome Extension is marked for deprecation or not. Could someone with direct knowledge address this question?
I need to know if I need to request that my work replace the extension with the native Windows app or not. Does the company intend to keep feature parity?
What's the difference between the Postman plugin and the extension? (since they are different)
The Chrome version of Postman is not using the same runtime for execution of requests & test scripts. It is recommended to transit to the native client. Especially when you plan to use Postman collections with the CLI client Newman.
You can read a blog post of the company on this topic here: Blog post on Chrome Extension vs. native app
We're encouraging Postman Chrome users to transition to the the Mac or Windows app when convenient, and to the Linux app when available, by heading to https://www.getpostman.com/apps and downloading the correct app. Going forward, we will be watching to see how Chrome OS app development proceeds, to make sure we provide the right tools for our community.
Since chrome apps will retire this year, is there any good replacement for it? I have a webclient which runs locally inside a chrome app with support of a cardreader for login to the webserver. Since all the hardware related things are managed inside the chrome app manifest and within the chrome api it is difficult to find a good replacement for this, any idea?