What is Chrome Canary and how is it different from Google Chrome - for Linux users?
2014-03
YumYumYum
Chrome has 3 releases - a regular release, a dev release and canary. Canary is simply a much newer release thats not as well tested, but has the latest shiny stuff. After a while the version that was released in the canary channel gets any bugs that are found fixed, then filters downward to dev, and then to the regular release. Other than the lack of testing, and possibly not having all the bugs fixed, canary is merely chrome FROM THE FUTURE
In short, you get cool stuff, but it might crash horribly. On the other hand, you don't have to use it as a primary (in fact, you cannot set it as default) browser. Its mainly useful if you like living dangerously and want to test bleeding edge features
Bit confuse.
Well Canary is the latest and the rest is for stable use like others said FROM the FUTURE.
But this question is about Linux user point of view. As i am 100% (CentOS, Fedora, ArchLinux, Ubuntu, FreeBSD) user and i unfortunately do not have permanent Mac or Windows development hardware/software.
How can i get Google Canary? When someone say please debug it with only Google Canary not with Google Chrome Browser or Chromium browser???
Please suggest
Journeyman Geek
That looks awefully familiar and there's a partial answer to your question in the comments
There's no official canary release for linux - There's releases for windows, and I believe OS X only. If you really must run canary in linux, it does seem to work in wine. Canary merely is an official, nightly build for windows and OS X.
The official explaination is that the nightly builds of chromium work perfectly well (other than a few plugins) due to logistical reasons. I suppose since linux covers a wider array of distributions, and hardware.
If you REALLY need a bleeding edge chrome build, go with a nightly build for the distribution or try it out in wine.
arathorn
I am specifying a custom user agent in Google Chrome in order to access a legacy web site on my company's intranet (the site is needlessly requiring IE). I created an application shortcut for the site and added the --user-agent parameter to the shortcut.
If I launch this shortcut without Chrome already running, things work fine. However, if I launch the application shortcut when another Chrome window is already open, the '--user-agent' parameter is ignored and the normal user-agent is used.
So, it appears that whatever user agent string is used when the first Chrome window is opened, that's what will be used for all future windows or application shortcuts. Is there any way to get around this behavior?
Lasse V. Karlsen
What you can do is create multiple profiles. This means that windows will not be shared, and likewise with favorites, cache, home-screen content, cookies, etc., but you'll be able to make your shortcut work the way you wanted it to.
First, follow the steps in this article here to create a secondary profile for Google Chrome: Create Separate Profiles in Google Chrome for Family Members and Stay Extra Safe.
Secondly, modify the shortcut by tucking on your --user-agent parameter. For instance, here's the command line I used to test:
"path\to\chrome.exe" --user-data-dir="..\User Data\Test" --user-agent="Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0)"
Now you can double-click on your regular Chrome shortcut, and this new shortcut, and each will open their windows in distinct sessions, with their own user agents.
BenA
The application window may be picking up and sharing the session started by your other window. If you aren't attached to browsing history etc. you could try tagging your shortcut with the --incognito parameter as well. Worth a shot!