I am working on a chrome extension that plans to use Chrome's upcoming API chrome.commands for defining global keyboard shortcuts.
This API will possibly be released in Chrome 25 (says here) and it is currently available in Canary, Dev and Beta. (have tested on Canary but not tried on Dev or Beta yet).
My question is: is there a way to enable this API in the current stable version of Chrome? I have tried enabling "Experimental Extension APIs" but that is not helping.
If you look at Source Code of Say 23.0.1248.0 here, you do not find references for these code!, So they are undefined in any older revisions.
Related
I have created an Opera extension, but have a question about the "manifest.json" file.
Specifically, I'm not sure what version I should put in "minimum_opera_version".
According to the documentation (which all points to the chrome developer API), based on the API calls I make the minimum version is Chrome 26.
However what version of Opera is that? How can I figure out what minimum version of Opera the extension requires?
Opera stable is now at version 49. First ChrOpera was ver 15. It's mainly those on XP that might need to resort to a much older build than current. You don't need to state minimum_version at all in the manifest.
The minimum_opera_version usually depends on the APIs you use in your addon. For example if you use Alarm API in your add-on then check from which version of Opera does the support for Alarms API exists and configure accordingly.
-> https://dev.opera.com/extensions/apis/
I built an extension for Chrome and Firefox and I am going to release it, soon. Do I have to check for the browser version the user is running or do the stores of Chrome/Firefox automatically check which version is needed and set this as a condition for downloading the extension?
Both browsers offer you a way to specify a minimum browser version in the extension's manifest.
For Chrome: minimum_chrome_version manifest key.
For Firefox (note, this will make the manifest incompatible with Chrome): applications.gecko.strict_min_version manifest key.
I'm not aware as to what happens on first install if the latest update requires a higher version, but an older version that fits exists - needs testing whether an older version will be offered or it will be marked as incompatible.
In case of automatic updates, the users will be stuck on last compatible version. Which makes it slightly problematic to inform them of this..
I've got a problem while trying to install rutoken plugin for Google Chrome v. 40.0.2214.115 (64-bit) on Ubuntu 14.04.
That's what I try:
Download plugin from http://www.rutoken.ru/support/download/rutoken-plugin/ and unpack files, so I had librtpkcs11ecp.so, npCryptoPlugin.so files.
Create a directory for plugins, in the Google Chrome's installation directory.
sudo mkdir /opt/google/chrome/plugins
Copy *.so files to the plugins directory.
Then I've restarted Chrome:
google-chrome -–enable-plugins
The problem is that when I run chrome://plugins/ there is no such plugin in a list.
It seems Java JRE is not more working on Chrome
https://askubuntu.com/a/590181
NPAPI support by Chrome
The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI, which has long been, and currently is, supported by all major web browsers. Google announced in September 2013 plans to remove NPAPI support from Chrome by "the end of 2014", thus effectively dropping support for Silverlight, Java, Facebook Video and other similar NPAPI based plugins. Recently, Google has revised their plans and now state that they plan to completely remove NPAPI by late 2015. As it is unclear if these dates will be further extended or not, we strongly recommend Java users consider alternatives to Chrome as soon as possible. Instead, we recommend Firefox, Internet Explorer and Safari as longer-term options.
I installed plugin updated but I face issue at testing time plugin not work properly in Chrome using link http://java.com/en/download/installed8.jsp?detect=jre If you got message "This plug-in is not supported" then follow following steps:
In your URL bar, enter:
chrome://flags/#enable-npapi
Click the Enable link for the Enable NPAPI configuration option.
Click the Relaunch button that now appears at the bottom of the
configuration page.
and test it again using http://java.com/en/download/installed8.jsp?detect=jre link.
I am making a website using WinJS 3.0.1, the last "stable" version as far as I know, and everything worked as a charm until I tried to create a ContentDialog following the instructions from http://try.buildwinjs.com and I discovered that that control is not included in that build, even if it was in previous versions of the library. The dialog will show up with pre 3.0 builds, but they only work on IE, so they are not a viable option.
Why is ContentDialog missing, has it been deprecated? Should I use other control or will it be added again in a coming version?
I've been searching through Microsoft documentation but I haven't found anything that explains why ContentDialog is not longer available, so any info is helpful.
Our current production version is PC 11.52 patch1 and our company is going to start IE11 roll out soon. We don't have many issues with our current production version so we would like to use it. But 11.52 doesn't support IE11. Because full migration needs lots of work (we have more than 100 projects), we are investigating alternative solutions. We tested 11.52 Vugen with IE11 and it seems, that Vugen can record scripts in WinInet mode. Would it be possible to record scripts using WinInet level capture and run them using Sockets? Is there some limitations using WinInet capturing and what pitfalls this approach might bring?
I don't know about PC 11.52 but I can answer regarding LoadRunner 11.52 (VuGen 11.52) It doesn't support IE11 because in IE11 Microsoft added some API which we had to add to the LoadRunner in order for it to work. The API was officially added in version 12 but a patch exists for version 11.52. The problem is that the patch is not available for direct download so you will have to open a support case. When you open the case please describe the problem and ask the patch for defect (77102).
EDIT: If you ask the same question on the official LoadRunner support forum then the support staff will be able to attach the file directly.