Saturday, June 9, 2012

[Gd] Fridaygram: IPv6 day, transit of Venus, game gifs

| More

Google Developers Blog: Fridaygram: IPv6 day, transit of Venus, game gifs

Author Photo
By Scott Knaster, Google Developers Blog Editor

340 trillion trillion trillion is our new favorite number. This past Tuesday was World IPv6 Launch, a huge step forward in making sure the Internet doesn’t run out of IP addresses in the near future. Until now, the universe has been using 32-bit addresses for devices on the Internet. The new version, IPv6, uses 128 bits, which increases the number of available addresses from a mere 4.3 billion to more than 340 undecillion, or more precisely, 340,282,366,920,938,463,463,374,607,431,768,211,456. So, that’s a lot.

From astronomical numbers to a rare astronomical event: the transit of Venus across the sun. This event was a big deal for NASA’s Solar Dynamics Observatory (SDO), a spacecraft that studies the sun. The SDO and its humans produced this breathtaking video made up of images from the transit. This is way better than what you saw with your welder’s goggles.

Finally, with all this advanced technology, it’s nice to go retro now and then. You can do that by enjoying these animated GIFs of video games, for when you just can’t find your 8-bit game system. (Hat tip: Boing Boing).

Each week we publish Fridaygram, featuring stuff from Google and beyond that you might have missed during the week. Fridaygram items aren't necessarily related to developer topics; they’re just interesting to us nerds. This week we say goodbye to Ray Bradbury as he departs Earth.

Friday, June 8, 2012

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Stable channel has been updated to 19.0.1084.56 for Windows, Linux, and Chrome Frame. This build contains a new version of Flash Player (11.3), in addition to some minor stability fixes.

Full details about what changes are in this build are available in the SVN revision logInterested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Anthony Laforge
Google Chrome


Thursday, June 7, 2012

[Gd] Try Chrome in Metro mode

| More

Chromium Blog: Try Chrome in Metro mode

Back in March, we began work on a Metro-style enabled desktop browser, a version of Chrome that will run in both the Metro and desktop environments of Windows 8 on x86. (Chrome won’t run in WinRT, i.e. Windows 8 on ARM processors, as Microsoft is not allowing browsers other than Internet Explorer on the platform.) If you’re running the Release Preview of Windows 8, you’ll be able to try Chrome in Metro mode in the next Chrome Dev channel release by setting it as your default browser.

The initial releases of Chrome in Metro mode will include integration with the basic Windows 8 system functionality, such as charms and snap view. Over the next few months, we’ll be smoothing out the UI on Metro and improving touch support, so please feel free to file bugs. We’re committed to bringing the speed, simplicity, and security of Chrome into Windows 8, and we look forward to working with you on it.

Carlos Pizano, Software Engineer and Metro Gnome

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 20.0.1132.27 for Windows, Mac, Linux, and Chrome Frame. This build contains updates to v8 ( and fixes for bugs and stability.

Full details about what changes are in this build are available in the SVN revision logInterested 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


Wednesday, June 6, 2012

[Gd] Chrome for Android Beta Update

| More

Chrome Releases: Chrome for Android Beta Update

Chrome for Android Beta has been updated to 0.18.4531.3636 on Google Play.  In addition to changes through Chrome 18.0.1025.166 and a minor reorganization of Settings options, this update focuses primarily on stability and performance improvements.

Known issues:

  • 113041 : No way to auto-hide the toolbar
  • 114964 : Error pages are not optimized for mobile / Android devices
  • Other notable issues listed here

If you find a new issue, please let us know by filing a bug.  More information about Chrome for Android is available on the Chrome site.

Srikanth Rajagopalan
Google Chrome

[Gd] Recommendations for building smartphone-optimized websites

| More

Official Google Webmaster Central Blog: Recommendations for building smartphone-optimized websites

Webmaster level: All

Every day more and more smartphones get activated and more websites are producing smartphone-optimized content. Since we last talked about how to build mobile-friendly websites, we’ve been working hard on improving Google’s support for smartphone-optimized content. As part of this effort, we launched Googlebot-Mobile for smartphones back in December 2011, which is specifically tasked with identifying such content.

Today we’d like to give you Google’s recommendations for building smartphone-optimized websites and explain how to do so in a way that gives both your desktop- and smartphone-optimized sites the best chance of performing well in Google’s search results.

Recommendations for smartphone-optimized sites

The full details of our recommendation can be found in our new help site, which we now summarize.

When building a website that targets smartphones, Google supports three different configurations:

  1. Sites that use responsive web design, i.e. sites that serve all devices on the same set of URLs, with each URL serving the same HTML to all devices and using just CSS to change how the page is rendered on the device. This is Google’s recommended configuration.

  2. Sites that dynamically serve all devices on the same set of URLs, but each URL serves different HTML (and CSS) depending on whether the user agent is a desktop or a mobile device.

  3. Sites that have a separate mobile and desktop sites.

Responsive web design

Responsive web design is a technique to build web pages that alter how they look using CSS3 media queries. That is, there is one HTML code for the page regardless of the device accessing it, but its presentation changes using CSS media queries to specify which CSS rules apply for the browser displaying the page. You can learn more about responsive web design from this blog post by Google's webmasters and in our recommendations.

Using responsive web design has multiple advantages, including:

  • It keeps your desktop and mobile content on a single URL, which is easier for your users to interact with, share, and link to and for Google’s algorithms to assign the indexing properties to your content.

  • Google can discover your content more efficiently as we wouldn't need to crawl a page with the different Googlebot user agents to retrieve and index all the content.

Device-specific HTML

However, we appreciate that for many situations it may not be possible or appropriate to use responsive web design. That’s why we support having websites serve equivalent content using different, device-specific, HTML. The device-specific HTML can be served on the same URL (a configuration called dynamic serving) or different URLs (such as and

If your website uses a dynamic serving configuration, we strongly recommend using the Vary HTTP header to communicate to caching servers and our algorithms that the content may change for different user agents requesting the page. We also use this as a crawling signal for Googlebot-Mobile. More details are here.

As for the separate mobile site configuration, since there are many ways to do this, our recommendation introduces annotations that communicate to our algorithms that your desktop and mobile pages are equivalent in purpose; that is, the new annotations describe the relationship between the desktop and mobile content as alternatives of each other and should be treated as a single entity with each alternative targeting a specific class of device.

These annotations will help us discover your smartphone-optimized content and help our algorithms understand the structure of your content, giving it the best chance of performing well in our search results.


This blog post is only a brief summary of our recommendation for building smartphone-optimized websites. Please read the full recommendation and see which supported implementation is most suitable for your site and users. And, as always, please ask on our Webmaster Help forums if you have more questions.

Posted by , Webmaster Trends Analyst


[Gd] Fire Up Your Computer: The 2012 Google Apps Developer Challenge is Here!

| More

Google Apps Developer Blog: Fire Up Your Computer: The 2012 Google Apps Developer Challenge is Here!

Updated to add links to the #gappschallenge hashtag and to Google Apps Script.

In the past year, the Google team has been engaging with local developers by running various Google conferences and Google+ Hackathons, showcasing creative applications, and supporting Tech Hubs. Since we are always looking for opportunities to encourage (and challenge!) you, we are looking forward to giving developers the opportunity to take on this year’s challenge, which will focus on Google Apps Script, Google Apps and Google Drive APIs.

With the Google Apps Developer Challenge, we hope developers across the globe will find new and innovative ways to use Apps Script, Apps and Drive APIs to build cool apps. This challenge is particularly unique as the APIs are available to a large community of developers who code in a variety of languages that include Java, PHP, Python, and .Net.

We will be working in collaboration with our Google Developer Groups (also known as GTUGs) and Google Business Groups to organize events and prepare for this challenge. Make sure to join your local community so that you are aware of meet ups.

How familiar are you with the various Google Apps and Drive APIs? If you aren’t familiar, make sure to read up about Google Apps Script, Google Apps and Drive APIs on Google Developers. Use the Chrome Web Store as a source of inspiration. Create an innovative application using Google Apps Script, Google Apps, and Drive APIs. If your application is the best within one of the three categories defined below in your region, you could win a prize of $20,000 dollars! Google is also committed to nurturing the next generation of computer scientists as well as encouraging more women to get into coding, so we have special prizes for all-student or all-female teams that make the second round — $1,000 dollars.

Fans Connect Online, one of the winners of last year’s Android Developer Challenge

The first round of submissions will start on the 24th of August 2012. The categories are

  • Enterprise / Small Business Solutions e.g., Accounting, Sales, Workflow, Collaboration
  • Social / Personal Productivity / Games / Fun
  • Education / Not for Profit / Water / Food & Hunger / Health

Make sure you read all the details about the competition on the Google Apps Developer Challenge page and follow the hashtag #gappschallenge on Google+ for any additional updates.

What are you waiting for? Get coding!

Chukwuemeka Afigbo profile | blog

Chukwuemeka is a Program Manager at Google with the Emerging Markets Outreach team where he works closely with developers, startups, businesses and IT professionals in the region to successfully grow their business around Google Developer Tools and APIs. His current mission is to drive developer internet content in Sub Saharan Africa.


Tuesday, June 5, 2012

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Chrome Stable channel has been updated to 19.0.1084.54 on Mac to support the transition to OS-X Mountain Lion.   

Full details about what changes are in this release are available in the SVN revision log. If you find a new issue, please let us know by filing a bug.

Anthony Laforge
Google Chrome

[Gd] Dev Channel Update

| More

Chrome Releases: Dev Channel Update

The Dev channel has been updated to 21.0.1163.0 for all platforms.  This update contains:


  • Updated V8 -

  • Added support for (pointer) and (hover) CSS media queries so sites can optimize their UI for touch when touch-screen support is available.

More details about additional changes are available in the svn log.  You can find out how to change to the Dev channel, or any channel, on  If you find a new issue with this release, please shoot us a bug report.

Jason Kersey
Google Chrome

Monday, June 4, 2012

[Gd] Easier domain verification

| More

Official Google Webmaster Central Blog: Easier domain verification

Webmaster level: All

Today we’re announcing a new initiative that makes it easier for users to verify domains for Google services like Webmaster Tools and Google Apps.

First, some background on this initiative. To use certain Google services with your website or domain, you currently have to verify that you own the site or domain, since these services can share sensitive data (like search queries) or operate Internet-facing services (like hosted email) on your behalf.

One of our supported verification methods is domain verification. Currently this method requires a user to manually create a DNS TXT record to prove their ownership. For many users, this can be challenging and difficult to do.

So now, in collaboration with Go Daddy and eNom, we’re introducing a simple, automated solution for domain verification that guides you through the process in a few easy steps.

If your domain name records are managed by eNom or Go Daddy, in the Google site verification interface you will see a new, easier verification method as shown below.


Selecting this method launches a pop-up window that asks you to log in to the provider using your existing account with them.


The first time you log in, you’ll be asked to authorize the provider to access the Google site verification service on your behalf.


Next you’ll be asked to confirm that you wish to verify the domain.


And that’s it! After a few seconds, your domain should be automatically verified and a confirmation message displayed.


Now eNom and Go Daddy customers can more quickly and easily verify their domains to use with Google services like Webmaster Tools and Google Apps.

We’re also happy to share that Bluehost customers will be able to enjoy the same capability in the near future. And we look forward to working with more partners to bring easier domain verification to even more users. (Interested parties can contact us via this form.)

If you have any questions or feedback, as always please let us know via our webmaster help forum.

Posted by Anthony Chavez, Product Manager

[Gd] Accelerated CSS Filters Landed in Chromium

| More

Chromium Blog: Accelerated CSS Filters Landed in Chromium

CSS filters are a powerful, easy-to-use visual effects tool for web developers. Filters can manipulate the appearance of any HTML element and can be stacked together to create unique effects -- all with a single line of CSS. Chromium GPU accelerates these filters to make them super fast. CSS filters are new in Chromium 19.

The current set of supported filters in Chromium include many that are familiar to web developers with image processing experience, such as sepia, saturation, opacity, and blurs. If you’re a web designer looking to add dynamic visuals to your next page layout, a developer building a photo editing app, or a game developer looking for an easy way to add effects to your next title, CSS filters can help you get there easily.

img { -webkit-filter: sepia(100%) contrast(200%) blur(5px) }

GPU acceleration of these filters brings their performance to the point where they can be used for animating elements in conjunction with CSS animations powered by -webkit-transition or even HTML5 video tags.

To get a sense of how much you can do with CSS filters, check out this interactive abstract painting app.

For more info on CSS filters, including a full list of those available in Chromium and how to use them, check out the new CSS Filter tutorial on HTML5Rocks.

Posted by Stephen “Rose-Colored Glasses” White, Software Engineer

[Gd] Beta Channel Update for Chromebooks

| More

Chrome Releases: Beta Channel Update for Chromebooks

The Beta channel has been updated to 20.0.1132.22 (Platform version: 2248.42.0) for Chromebooks (Acer AC700, Samsung Series 5, Samsung Chromebook Series 5 550, and Samsung Chromebox Series 3, and Cr-48).  This release contains functional, security and stability improvements. Machines will be receiving updates to this version over the next several days.

Highlights of these changes are:

  • Update to Chrome 20
  • Switched to open source touchpad driver on Cr-48
  • Introduced redesigned UI to Cr-48
  • Security fixes

Known issues:

  • 29329 - Cr-48 Scrolling not consistent with resting finger.

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