I want to use stable chrome version at pptr, so i search https://omahaproxy.appspot.com/ for finding chromium build.
but build 902210 is not in chromium browser snapshot( https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html)
is there something another way to find stable chromium build?
I had the same issue so here is what I found in case it helps:
On https://www.chromium.org/getting-involved/download-chromium, it is written "you can get a build of Chromium 44.x which should mostly match the stable release" and "sometimes you may have to decrement the commit number until you find one".
I searched the latest version number (which is currently 94.0.4606.81) on https://omahaproxy.appspot.com/ but cannot find its build number (911515, known as Branch Base Position on the previous link) on https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/.
So I decremented the number until I find one matching, like explained previously and I found 911494: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/911494/
When I downloaded this Chromium version, in "About Chromium", it displayed "Version 94.0.4606.0 (Developer Build) (64-bit)". Which almost matches 94.0.4606.81.
On https://githubmemory.com/repo/Bugazelle/chromium-all-old-stable-versions/issues/2, I read "You cannot install a stable Chromium version downloaded from chromium-browser-snapshots because there are absolutely no Chromium stable versions there." and "It is recommended to compile Chromium yourself to have a similar stable version... or find third-parties builds.".
Linux distributions like Ubuntu provide a stable Chromium package. Otherwise if we don't want to compile the stable version, we can get the closest developer version like explained previously.
Related
I understand what Canary is. But it's pretty useless if you don't know what beta features are available. So is there a place where this information can be found? I've been googling but can't find anything.
Chrome Canary isn't the Chrome Beta, it's built daily and is the bleeding edge of Chromium development. Writing digested changelogs isn't feasible for daily builds.
You can have a look at every change here:
https://chromium.googlesource.com/chromium/src/
click on the current tag, e.g. 62.0.3168.0 and then on log.
For Chrome Beta, the Chromium Blog is a good resource:
https://blog.chromium.org/
e.g. for Chrome 60 Beta:
https://blog.chromium.org/2017/06/chrome-60-beta-paint-timing-api-css.html
Releases (Stable, Dev, Beta) in more detail:
https://chromereleases.googleblog.com/
Here's how I understand the google browser differences:
Chrome - Production release (the one we're currently using, stable version)
Canary - Test release before new production release (Version prior to Chrome release)
Chromium - Dev release and available in Linux (maintained by Ubuntu developers, no auto-update of version - user triggered)
Are there any other points that I missed? And in terms of development, is there any other consideration if I use Chromium and Canary rather than Chrome? Like caching, compatibility, cookie, performance and etc. (bugs?)
Your interpretation is correct
Canary is basically a (near) nightly release built from the current tip of tree of the Chrome repo. It's the bleeding edge of development and so you should expect crashes and bugs but it's the quickest way to test recent changes to chrome. (Aside from building ToT yourself)
Aside from Canary, there's also the Dev channel which is a slightly longer development release, usually about weekly, but still built from the bleeding edge tip-of-tree. Beta channel is a long running branch that's the upcoming release and is generally quite stable/bug free.
The order from "freshness" to "stable": Canary -> Dev -> Beta -> Stable
Chromium is the name of the open-source project from which Chrome is built. A Chromium build is basically equivalent to Chrome but doesn't include proprietary bits (Flash plugin, codecs, etc) or official Google branding (icons, etc).
Compatibility in terms of web-facing APIs between the different versions should be essentially the same except, of course, for intended upcoming changes. In general, changes that occur in Canary, Dev, and especially Beta, are intended to make it to Stable channel so it's a good idea to test your apps against Beta to make sure your app will continue to function as expected once the Beta is promoted to Stable. You can find upcoming changes to Web APIs at ChromeStatus
In Canary and Dev, you're more likely to run into unintentional bugs that creep in during development. If you'd like to help Chrome development you can file bugs for these at the Chromium bug tracker (use this for bugs you find in Stable/Beta channel too!)
In terms of performance, a hand-built Chromium will depend on who built it and with what flags. The performance between Canary/Dev/Beta/Stable should be comparable and indicative of the final stable release.
I can't seem to find a clear answer on this anywhere.
How far back is it backwards compatible? Do I have to be concerned about creating multiple versions of the extension?
Thanks
"manifest_version": 2 itself does not cause any incompatibility issues.
But you can easily make a mistake and create an extension which is backwards-incompatible, by using features/APIs which are introduced in Chrome 18 or later (manifest v2 came with Chrome 18).
I suggest to not worry about the old manifest version any more, because only Chrome 17- is affected. As of writing, the current stable version is 23. Hardly anyone is using Chrome 17 any more.
See also
How to upgrade extension to manifest v2 and remain backwards compatible? (Stack Overflow answer)
Tutorial: Migrate to Manifest V2 (Official documentation, apply the tips in the reverse order)
Manifest version 2 extensions have to use "background" instead of "background_page" (and the manifest cannot contain it or Chrome refuses to load the extension), but "background" is not supported in older versions of Chrome. This is the main problem.
The only work around I can think of is to publish multiple versions of your extensions and ask users to download and install the correct version.
I need to check a bug in Google Chrome for specific version like 14.0.802.30. How can I get the pervious version for that? Also, how can I switch off automatic update functionailty of Chrome?
Some old Chrome-Versions can be found on oldapps.com if you can't find the version there, you can maybe use the corresponding Chromium release? Its basically Chrome minus the Google-Spyware. For Operating Systems other than linux you have to build your own version tough (easy to follow instructions are published on the website).
Chromium-Releases can be found here
Edit: The bug that caused this problem has been fixed. The #version tag now works in the stable release. See Issue 30760
Hey.
I've been wondering how I might set the version number displayed for user-scripts in Chrome's extension tab
(source: advefir.com)
So far the obvious methods have failed:
// ==UserScript==
// #version 1.1.5
// #uso:version 1.1.5
// ==/UserScript==
I know Greasemonkey for Firefox doesn't use a version value, but since Chrome actually displays a version number, I thought it might.
Perhaps this is a feature that has not been implemented?
Or maybe it was never intended to be there, but it is there because extensions have version numbers, and user-scripts are currently installed as extensions?
(I'm using the Linux beta, version: 4.0.249.43, by the way)
Thanks.
Ok, this appears to be a confirmed bug now. (Issue 30760)
Seems the standard #version meta-data is the correct usage, but it has not yet been implemented.
Edit: The #version tag now works in the stable release of Chromium (and, therefore, Chrome).
Or maybe it was never intended to be there, but it is there because extensions have version numbers, and user-scripts are currently installed as extensions?
I think so.
Version number used for updating extensions. User scripts currently can not update. "Update extensions now" button doesn't work for them.
Fixed, but apparently not yet released:
http://code.google.com/p/chromium/issues/detail?id=30760#c16