I found a bug in my chrome extension soon after I published. Can I revert to the stable version and avoid users getting the buggy version that just got published?
Related
I was trying to make ObjectSpy work with Chrome browser but its unable to identify objects.
Whenever trying to identify getting this: WinObject("Chrome Legacy Window").
I tried reinstalling UFT and chrome and Microfocus extension for chrome but it didn't help.
I have downloaded extension from internet and its shows the version as Micro Focus UFT Agent
2022.0.1.25. My UFT version is 14.53. I am not sure if its compatibility issue.
Please help.
UFT 14.53 is pretty old as far as supported browsers are concerned (July 2019), if possible I would suggest upgrading to the latest version (upgrades are included in the license).
Failing that you can try to remove the extension from Chrome and install the one that comes with your version of UFT (in <UFT installation dir>/Installations) although I'm not sure it will work with current versions of Chrome.
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..
Anybody know how to get the .MSI installer for an older version of Typescript - the download at the offical URL for version 0.9.1.1 is no longer available.
It seems newer version 1.0 or 1.0.1.0 is available, but that version is incompatible with my client's software which I am attempting to support.
Any idea how to get the specific version I need?
OK - found it. After some digging, there is a reference in the bowels of the Microsoft Download Center for many old versions of TypeScript.
Expand the 'Details' section and scroll down, click 'Download' link on desired version...
Suppose my extension is version 1.0. I write a new feature and release 1.1. Then I quickly realize I've shipped a bug, fix it, and release 1.2.
Now suppose a user with 1.0 is offline until after 1.2 is released.
Will they update to 1.2 or to 1.1?
Do users get updated to the latest version, or to the next version from the one they have?
Users always get the latest version. So you’ll have to integrate any update code for 1.1 in 1.2 as well.
Every few hours, the browser checks whether any installed extensions or apps have an update URL. For each one, it makes a request to that URL looking for an update manifest XML file. If the update manifest mentions a version that is more recent than what's installed, the browser downloads and installs the new version.
— http://developer.chrome.com/extensions/autoupdate.html
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.