Google's Geolocation API Comes to the Browser

The Geolocation API can run on any browser that has Google Gears and automatically will run on Android and Google's browser, Chrome.

Google currently knows your approximate location for when you do searches only via IP data, personalized search data or other, less exact methods. But now, if the browser can detect wifi locations and/or cell towers, Google will know where you are, almost to your exact location. GPS is supported, but most laptops or desktops do not have GPS devices built in yet (yes, yet).

The reaction to this from advertisers and searchers are split. A WebmasterWorld thread has advertisers excited that Google's geolocation capabilities will be able to target their ads better. But searchers are not yet 100% comfortable with Google knowing their exact whereabouts, at all times while using Google properties. Personally, I am not about privacy - I actually am considering wearing a GPS enabled device with me at all time to track me where ever I go .

More on Google Chrome>>

Google readying fix for Chrome file download flaw

Chrome's JavaScript challenge to Silverlight

Google's Chrome browser

Google's Chrome Browser Not Yet Secure

Source- seroundtable 

Google readying fix for Chrome file download flaw

Just hours after the release of the Google Chrome browser last month, researcher Aviv Raff discovered that he could combine two vulnerabilities — a flaw in Apple Safari (WebKit) and a Java bug — to trick users into launching executables direct from the new browser. (Here’s a demo showing how Google Chrome users can be lured into downloading and launching a JAR (Java Archive) file that gets executed without warning.

Now, it looks like Google is finally taking the threat seriously with the release of a new Chrome version to developers that change the download behavior for files that could execute code.

From the changelog:

·          This [version] adds prompting for dangerous types of files (executable) when they are automatically downloaded.

·     The file is saved with a temporary name (dangerous_download_xxxx.download) in the download directory and the user is presented (in the download shelf and the download tab if opened) with a warning message and buttons to save/discard the download.

·          If discarded the download is removed (and its file deleted). If saved, download goes as usual. 

 Dangerous downloads not confirmed by the user are deleted on shutdown.

More on Google Chrome>

Google Chrome browser losing marketshare after initial surge

Google's Chrome Browser Not Yet Secure

Google's Chrome browser

Google Chrome browser losing marketshare after initial surge

NewScientist tracks down data suggesting that the bloom is off rose for Google's Chrome browser.
After initially seeing its share of the browser market jump as high as 3.1 percent, Chrome is now down to about 1.5 percent.
What led those users to dump the browser after giving it a test drive?
My wild guess: no Adblock Plus or equivalent.
Chrome is functional and attractive in almost every other way, but it's competing for the same tech-oriented user as Firefox. And Firefox has Adblock Plus.
With no other major distinguishing features (the speed difference is likely negligible to most users), why switch?
I suspect Google will be content to let Chrome molder in the background when it comes to desktop users.
But the company likely has much bigger plans in the mobile arena.
The G1 Android phone will use a modified version of Chrome, as will presumably other Android phones when they're released.
At that point, Chrome usage will likely soar, and that's the market Google wants to corner.
More on Google Chrome >>
Google's Chrome Browser Not Yet Secure
Speed test: Google Chrome Wins the race and beats Firefox, IE, Safari
Google's Chrome browser
Source- techblog.dallasnews