Unfortunately Google Chrome doesn’t currently support opening files without downloading them, which is a pain when dealing with .torrent files which must be manually opened after downloading. I’ve been doing things this way for a while, but today stumbled across a handy feature in µTorrent which solves this minor annoyance: monitoring a directory for .torrent files.
Under Options ? Preferences ? Directories, tick the bottom two boxes (Automatically load .torrents from and Delete loaded .torrents), then type or browse to the path where Chrome downloads your files. For me, it’s D:\Downloads.
You can keep Delete loaded .torrents unticked if you like, but for me this option is a godsend as it saves me having to manually clear old .torrent files from my download directory.
To make the process as seamless as possible, make sure that Chrome’s Ask where to save each file before downloading option is unticked:
When attempting to log into my Tesco Bank savings account recently, I was greeted with a message stating that my browser – the latest stable build of Google Chrome – is unsupported:
Tesco’s security concerns seem unfounded given that Google Chrome – which, incidentally, is based on same the WebKit rendering engine as Safari - was recently proven to be one of the most secure browsers.
Also, despite the site’s recommendation of a “modern version of Firefox”, I found that I was also prevented from logging in using the latest version of Firefox 3.6. Trusty (or should that be rusty?) old Internet Explorer 6 seems to work fine, and that’s not a particularly secure browser by any stretch of the imagination!
Strangely, I’m able to log into my Tesco Bank credit card account just fine with Chrome; it’s just the savings area that locks me out.
Fortunately the only reason I logged in was to withdraw my full balance ready to add to my 2010/11 ISA, but if I were looking to continue saving with Tesco, their short-sighted approach to browser support would certainly have me thinking twice.
Google offer a standalone installer for the Windows build of Google Chrome, as opposed to the standard download which is actually just a small stub application that connects to Google’s servers to download and install the actual browser.
The offline installer is handy if you have a number of machines on which to install or update Chrome, but unfortunately Google haven’t updated it recently, so you end up with version 184.108.40.206 rather than the latest all-singing, all-dancing, extension-supporting version 220.127.116.11.
You can of course update to 18.104.22.168 from the About screen, but this defeats the purpose of using the standalone installer in the first place, and you may be unlucky enough to be on a corporate network which breaks the in-browser upgrade functionality.
By using Fiddler2 to monitor the activity of the stub installer, I was able to establish that it connects to the following google.com URL to download the latest build:
The beta version of Google Chrome has supported extensions for many months, but Google today released a stable Windows version of Chrome 4.0 which supports extensions together with a handful of other features and improvements. Both The Official Google Blog and the Google Chrome blog have full details.
To get the update, click the About Google Chrome menu option (viathe spanner icon) and click Check for Updates.
I’ll keep this post short and sweet as I’m now off to the extensions gallery to pick up some new enhancements for my favourite browser!
I’m currently testing out Google Chrome to see if it can replace Firefox as my main day-to-day browser, and have so far been quite impressed. However I hit a stumbling block when I tried to watch some tutorial videos on Microsoft’s site and was prompted to install Silverlight 3, which is unfortunately not supported on Chrome.
The easy thing to do at this point would have been to drop into Firefox or IE and install Silverlight from there, but where’s the fun in that?