Google Chrome Browser

Dev Channel Update

admin — Wed, 16 May 2012 00:15:00 +0000

The Dev channel has been updated to 20.0.1132.8 for Windows, Mac, Linux, and Chrome Frame. This build contains updates to V8 (3.10.8.5) and several other fixes. Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome

Connect with Web Intents

admin — Tue, 15 May 2012 20:35:00 +0000

Last year we proposed the Web Intents API to help web applications integrate with one another with minimal effort. We've now enabled an experimental version of the API in the most recent stable version of Chrome, to gather feedback from the web community and shape the future of the Web Intents API.

This prototype version of Web Intents makes it easier for developers to try out the API and experience its benefits first hand:

Developers who build client apps will be able to easily include functionality from other web services (e.g., photo editing).
Developers creating those services will no longer need to invest time and resources to negotiate and build hardcoded integrations - they can just focus on offering a great quality product with the integration facilitated by the API.

In addition, this implementation of Web Intents can help the design discussions in the W3C web intents open standards list. After all, it's impossible to build a complex API—especially one that requires an ecosystem of apps—without feedback from web developers using it in the wild.

We expect that Web Intents will evolve significantly, potentially in backwards-incompatible ways, as feedback from real world usage trickles in. Because of its experimental status, the current live version is prefixed and only allows applications to register as services in their Chrome Web Store app manifest.

Once the API is stable, we plan to remove this restriction.

To learn more on how to use the experimental Web Intents API check out the Web Developers' Guide to Web Intents in Chrome. If you choose to experiment with Web Intents, be sure to follow our discussion group, where we'll announce any impending breaking changes in Chrome's implementation.

Posted by James Hawkins, Software Engineer

The Dev channel has been updated to 20.0.1132.7 for Chromebooks (Acer AC700 , Samsung Series 5, and Cr-48)

admin — Tue, 15 May 2012 17:01:00 +0000

The Dev channel has been updated to 20.0.1132.7 (Platform versions: 2268.9.0) for Chromebooks (Acer AC700 , Samsung Series 5, and Cr-48).

This build contains a number of new features, as well as security & stability improvements. Some highlights of these changes are:

Update Netflix plugin to 2.0.2
Fix for blank pages when switching between tabs
Stability and security updates

Known issues:

126794: Facebook.com photo uploading and Yahoo mail attachment fails
126843: Flash fails to record audio

If you find new issues, please let us know by visiting our help site or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue’ under the wrench menu.

Josafat Garcia
Google Chrome

Google Chrome Might Be Coming On iOS Soon

admin — Tue, 15 May 2012 16:51:30 +0000

Macquarie Equities Research released a report stating that Google’s Chrome browser might be coming to iOS device. The report does not state when it might arrive on the Apple’s app store, however, it states that it could be as soon as Q2 of 2012 and if it doesn’t land on the app store by that time, it is definitely arriving by the end of this year.

As much as we would like to see the Chrome browser on iOS devices — iPhone, iPad, and iPod Touch, Apple doesn’t allow third party browser app to be set as a default app for the device which limits the usability of the app. For example, any links within an email, text messages will open on default browser (Safari) on any iOS devices.

Chrome browser on desktop is highly successful browser with about 18.57% of browser market share falling only slightly behind Mozilla Firefox. Google, also, recently released Chrome Beta for its own mobile operating system, Android. With the release of Chrome on iOS Google also might be able to get away with the huge chunk of money it spends on Apple for Google search on Safari browser. With Chrome browser, all the money that it will earn from the search, Google will be able to keep them with themselves.

However, we do not think Chrome for iOS will make it big for a simple reason that Apple does not allow third party apps to be set as default browser.

Google Chrome Might Be Coming On iOS Soon originally appeared on Techie Buzz written by Apurva Chaudhary on Tuesday 15th May 2012 12:51:30 PM under Tech News.

Frak, yeah, I'd use iPad if there was Google Chrome

admin — Tue, 15 May 2012 16:48:58 +0000

What timing. I posted my iPad for sale on Craigslist over the weekend -- and two people are jockeying to get ahead of the other to buy it today. But I'm suddenly unsure about selling, after seeing a Macquarie Capital report claiming that Chrome will come to iOS as early as this quarter. Hot damn!

I rarely make decisions based on rumors, nor should you. Besides, the "timing is unclear, but it could be as soon as Q2 and is very likely to be a 2012 event", according to Macquarie Capital. "Could" be this quarter and "likely" this year stink of pure speculation -- or big back door should there be no Chrome for iOS this year. In the end, I'll likely sell the iPad, but must convey this: Chrome would be a very good reason to buy an iOS device but be akin to Google cutting off one limb to save another.

Shine That Tablet's Chrome

Yesterday, Ian Betteridge and I bantered back and forth about Chrome and iOS on Google Plus. He called Google services on Apple devices a "pretty good experience", to which I responded: "I would agree about the Google ecosystem with iPhone (and iPad) if Chrome was option. That's the deal breaker for me, sadly. I'm seriously thinking about selling my iPad, for that reason -- and another: Galaxy Nexus is tablet enough for me, so far".

As expressed last week, "You can have iPhone 4S, I'll take Galaxy Nexus". But there's more. I find the Google and Samsung branded smartphone good enough replacement for my iPad, too. Chrome for Android is one reason, Galaxy Nexus' super sharp, 4.65-inch, 1280 x 800 resolution screen is the other. Repeating a sentiment from my Galaxy Nexus HSPA+ review: I'd by the phone just for Chrome, which currently is only available for Android 4 "Ice Cream Sandwich", in beta.

Presumably, Chrome would be available for the newest iOS version, which means broader distribution than Android, since Apple doesn't have the same fragmentation problem. Based on number of devices accessing Google Play during the previous 14 days, Ice Cream Sandwich accounted for just 4.9 percent of the Android install base on May 1. Chrome has limited reach at best on Android, while distribution could be enormous on iOS, assuming people using the browser on the desktop go mobile, too. There, Chrome is third-most used browser and closes on Firefox, according to Net Applications.

Chrome is a huge improvement over the stock Android browser. It's fast and flows, but sync capabilities, which include active tabs on the desktop, really stand out. Last week's huge Google+ for iPhone update shows that the search and information giant can deliver exceptional user experiences on iOS. Why shouldn't Chrome be same?

A TACtical Decision

The problem: Chrome for iOS, particularly iPad, removes an important reason to choose Android tablets over Apple's. Google gains in one area, while giving up somewhere else. If Google offered Chrome for iOS right now, I'd keep my iPad. How many other people considering Apple's tablet would choose it over an Android because of Chrome? You can help answer that question by taking our poll.

In April, with considerably smaller install base, iPad took decisive mobile browser usage share lead from iPhone, according to NetApps. More broadly, in the mobile device category, Safari has 63.84 percent usage share, compared to 18.87 percent for Chrome. Google's browser could make usage share leaps competing alongside Safari on iOS devices. The cloud-connected device era is all about mobile. Google should want Chrome on market-leading devices like iPad.

Then there are traffic acquisitions costs, which eat into Google search margins. Macquarie Capital: "If GOOG gains market share, it could reduce our estimate for Google.com TAC meaningfully". Google pays Apple to compete with Android -- and Chrome, for that matter -- via Safari's search bar. Google's TAC goes down when people use Chrome.

Something else: Google services have a cloudy future on Apple devices. There already are rumors Apple will ditch Google Maps for a home-grown option in iOS 6. I expect to see a Siri search service someday replace Google. Chrome for iOS would be an important anchor for Google services as Apple offers more of its own from the cloud.

Even then, Chrome faces hurdles placed by Apple. Based on the browsers currently available for iOS, Safari is default for mail and other services. So Chrome would be at disadvantage, as long as Apple only allows Safari to be default. However, surely Chrome could be default for Google services -- gulp, right?

From that viewpoint, Chrome will always be better on Android. That said, Chrome on iOS ought to be pretty good, and if Google is going to feed the hand that bites it, better to extend existing services rather than pay TAC to Apple.

My question for you: Would you use Chrome over Safari on iPad or iPhone? Please answer the question below and take our poll above.

Google Chrome Browser Coming to iOS? [iOS Blog]

admin — Tue, 15 May 2012 15:57:46 +0000

Business Insider reports on a new research note from Macquarie analyst Ben Schacter, who claims that Google is working to bring a version of its Chrome browser to iOS devices. According to the report, Apple "may already be reviewing" the app, which could debut before the end of the quarter.

Google Chrome browser for Android

Google currently splits ad revenue share with Apple for Google searches performed through Safari, a deal that currently sees Google paying Apple roughly $1 billion per year. With a potential Chrome browser for iOS leading to Google keeping all revenue for searches through the browser for itself, Google could see a significant financial benefit if it can achieve a substantial user base on iOS.

The problem for Google is that Apple does not make it convenient for users to take advantage of third-party browsers, with Safari alternatives like Opera and Dolphin representing only tiny fractions of iOS browser share. Systemwide calls for browser actions throughout iOS apps are linked to Safari, meaning that users have to take extra steps to use a different browser, with the inconvenience leading the vast majority of users to simply use Safari for their iOS browsing needs.

Chrome Likely Heading to iPhone and iPad

admin — Tue, 15 May 2012 15:15:00 +0000

According to a note published by Macquarie Equities Research, Google is working on an iPhone and iPad version of its Chrome browser, slated for launch sometime this year.More »

Google Chrome 19 arrives to the Stable Channel for Windows, Mac, Linux and Chrome Frame

admin — Tue, 15 May 2012 15:00:00 +0000

The Google Chrome team is happy to announce the arrival of Chrome 19 to the Stable Channel for Windows, Mac, Linux and Chrome Frame. Chrome 19 contains a number of new features like tab sync. More detailed updates are available on the Chrome Blog.

Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

[112983] Low CVE-2011-3083: Browser crash with video + FTP. Credit to Aki Helin of OUSPG.
[113496] Low CVE-2011-3084: Load links from internal pages in their own process. Credit to Brett Wilson of the Chromium development community.
[118374] Medium CVE-2011-3085: UI corruption with long autofilled values. Credit to “psaldorn”.
[$1000] [118642] High CVE-2011-3086: Use-after-free with style element. Credit to Arthur Gerkis.
[118664] Low CVE-2011-3087: Incorrect window navigation. Credit to Charlie Reis of the Chromium development community.
[$500] [120648] Medium CVE-2011-3088: Out-of-bounds read in hairline drawing. Credit to Aki Helin of OUSPG.
[$1000] [120711] High CVE-2011-3089: Use-after-free in table handling. Credit to miaubiz.
[$500] [121223] Medium CVE-2011-3090: Race condition with workers. Credit to Arthur Gerkis.
[121734] High CVE-2011-3091: Use-after-free with indexed DB. Credit to Google Chrome Security Team (Inferno).
[$1000] [122337] High CVE-2011-3092: Invalid write in v8 regex. Credit to Christian Holler.
[$500] [122585] Medium CVE-2011-3093: Out-of-bounds read in glyph handling. Credit to miaubiz.
[122586] Medium CVE-2011-3094: Out-of-bounds read in Tibetan handling. Credit to miaubiz.
[$1000] [123481] High CVE-2011-3095: Out-of-bounds write in OGG container. Credit to Hannu Heikkinen.
[Linux only] [123530] Low CVE-2011-3096: Use-after-free in GTK omnibox handling. Credit to Arthur Gerkis.
[123733] [124182] High CVE-2011-3097: Out-of-bounds write in sampled functions with PDF. Credit to Kostya Serebryany of Google and Evgeniy Stepanov of Google.
[Windows only] [124216] Low CVE-2011-3098: Bad search path for Windows Media Player plug-in. Credit to Haifei Li of Microsoft and MSVR (MSVR:159).
[124479] High CVE-2011-3099: Use-after-free in PDF with corrupt font encoding name. Credit to Mateusz Jurczyk of Google Security Team and Gynvael Coldwind of Google Security Team.
[124652] Medium CVE-2011-3100: Out-of-bounds read drawing dash paths. Credit to Google Chrome Security Team (Inferno).

And some additional rewards for issues with a wider scope than Chrome:

[Linux only] [$500] [118970] Medium CVE-2011-3101: Work around Linux Nvidia driver bug. Credit to Aki Helin of OUSPG.

[$1500] [125462] High CVE-2011-3102: Off-by-one out-of-bounds write in libxml. Credit to Jüri Aedla.

Many of the above bugs were detected using AddressSanitizer.

We’d also like to thank Aki Helin of OUSPG, Sławomir Błażek, Chamal de Silva, miaubiz, Arthur Gerkis and Christian Holler for working with us during the development cycle and preventing security regressions from ever reaching the stable channel. $9000 of additional rewards were issued for this awesomeness.

Full details about what changes are in this release are available in the SVN revision log. Interested in hopping on the stable channel? Find out how. If you find a new issue, please let us know by filing a bug.

Anthony Laforge
Google Chrome

Signing in to Chrome: Tab Sync

admin — Tue, 15 May 2012 14:12:42 +0000

Signing in to Chrome: Tab Sync Chrome syncs your tabs across all your devices, so you can access them from the "Other devices" menu on the New Tab page. Go to the Chrome menu and select "Sign in to Chrome." google.com	From: googlechrome Views: 22429 47 ratings
Time: 00:35	More in People & Blogs

Google Chrome Blog: Keeping tabs on your tabs

admin — Tue, 15 May 2012 12:00:00 +0000

Say you’ve found an awesome recipe on your work computer while... ahem... working hard at the office. But when you get back home, you can’t quite remember if it was two teaspoons of baking soda or two teaspoons of baking powder. Wouldn’t it be cool if you could pull up the same recipe on your home computer with one click?

With today’s Stable release of Chrome, you can. When you’re signed in to Chrome, your open tabs are synced across all your devices, so you can quickly access them from the “Other devices” menu on the New Tab page. If you’ve got Chrome for Android Beta, you can open the same recipe tab right on your phone when you run out to the store for more ingredients. The back and forward buttons will even work, so you can pick up browsing right where you left off.

Open tabs aren’t the only things that sync when you sign in to Chrome. Signing in to Chrome also syncs your bookmarks, apps, extensions, history, themes, and other settings. That way, when you sign in to Chrome, you can have your personal Chrome experience on all your devices. Just go to the Chrome menu and select “Sign in to Chrome.”

While Chrome will be updated to the latest Stable version over the next few days, the tab sync feature will be rolled out more gradually over the coming weeks. Thank you for your patience and we hope you enjoy staying in sync!

Posted by Raz Mathias, Software Engineer and Tab-Wrangling Server Jockey