Here they say that in June 2023 Manifest v2 extension will no longer run in Chrome: https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/
Does it also mean that it won't be possible to load manifest v2 extensions in developer mode? Are there any official links or statements about this?
There is this comment in the Chrome Extensions Google Group: "Yes, locally running manifest versions is dependent on the Chrome browser being able to run it - when this ceases in January 2023 this will also end."
Here: https://groups.google.com/a/chromium.org/g/chromium-extensions/c/H12F2kETGpg/m/mCmAaabTAwAJ
So apparently manifest v2 extensions will no longer be supported in developer mode from January 2023.
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.
So, now I am looking for a list of all the browsers and their versions which are supported by Selenium 2.0
I searched http://docs.seleniumhq.org/about/platforms.jsp also but it seems the document is not updated, as I cannot see FF later versions like 13 and 14 listed over there.
So far, I have just worked on FF 13, 14 and IE 8
Could someone suggest me any link or a list here the browsers with their versions?
Many thanks for any help!
Regards,
The officially supported browser versions are as follows:
IE: Versions 6-10 supported. Version 11 should work fine, but is untested. IE6 support is to be discontinued on 15 April 2014.
Firefox: Versions supported using native events are the current version, immediately previous version, current extended support release (ESR) version and immediately previous ESR release, as determined from the date of release of the Selenium components. The last public Selenium release at the time of this writing was on 27 August 2013, and at the time, that means the supported Firefox versions were 23 (current), 22 (previous), 17 (current ESR), and 10 (previous ESR). This is complicated by the fact that this version support is only applies to so-called "native events"; if you don't use native events, a much wider range of Firefox versions is supported.
Chrome: Version support is determined by the chromedriver exectuable used, and is available at the chromedriver download site, but is usually stated as the current and previous stable channel releases, the current beta channel release, and the current dev channel release, as determined by the date of release of the chromedriver executable.
Opera: The OperaDriver supports Opera 12.x. It is theoretically possible to use the chromedriver executable for Opera 15+, but Opera Software has yet to make the necessary changes in Opera to allow this.
which browsers are supported by Selenium 2.0.
Mind you, that Selenium 2 relies on on the drivers for each browser. What you should turn to, is the versions of IEDriver, ChromeDriver, FirefoxDriver, etc.
Each WebDriver supports a range of versions of the browser.
For example, chromedriver 2.2 works on Chrome v27-29 I believe. As far as a list goes, I think you'll have to dig. There aren't any sources i've found yet.
The Firefox driver is native to the main jar as a firefox extension so that's not as obvious but IE and ChromeDriver supported versions can be found on the driver download page. You can see on the page below that the latest chrome driver supports version 28-31. One thing you'll probably notice is that every time a new FF version comes out, typically less than a month later a new selenium jar will come out.
https://code.google.com/p/chromedriver/downloads/list
ChromeDriver server for win32 (v2.3.220795) supports Chrome v28-31
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.