Friday, April 12, 2013

[Gd] Beta Channel Update for Chrome OS

| More

Chrome Releases: Beta Channel Update for Chrome OS


The Beta channel has been updated to 27.0.1453.46 (Platform version: 3912.23.0) for all Chrome OS devices. This build contains a number of bug fixes, security updates and feature enhancements.
Machines will be receiving updates over the next several days.


Some highlights of these changes are:

  • Pepper Flash updated to 11.7.700.169
  • New Launcher positioning mode
  • Horizontal three finger scrubb moves between tabs
  • New folder hierarchy on file manager
  • Memory management optimization
  • Enhanced support for common wireless touchpads/mice
  • Updated Chrome Office Viewer extension

Known issues:
  • On Samsung Chromebooks, HTML5 video playback is not always smooth. (225563)

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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

Josafat Garcia
Google Chrome

URL: http://googlechromereleases.blogspot.com/2013/04/beta-channel-update-for-chrome-os_12.html

[Gd] Two New Videos About Testing at Google

| More

Google Testing Blog: Two New Videos About Testing at Google

by Anthony Vallone

We have two excellent, new videos to share about testing at Google. If you are curious about the work that our Test Engineers (TEs) and Software Engineers in Test (SETs) do, you’ll find both of these videos very interesting.

The Life at Google team produced a video series called Do Cool Things That Matter. This series includes a video from an SET and TE on the Maps team (Sean Jordan and Yvette Nameth) discussing their work on the Google Maps team.

Meet Yvette and Sean from the Google Maps Test Team



The Google Students team hosted a Hangouts On Air event with several Google SETs (Diego Salas, Karin Lundberg, Jonathan Velasquez, Chaitali Narla, and Dave Chen) discussing the SET role.

Software Engineers in Test at Google - Covering your (Code)Bases



Interested in joining the ranks of TEs or SETs at Google? Search for Google test jobs.

URL: http://googletesting.blogspot.com/2013/04/two-new-videos-about-testing-at-google.html

[Gd] A new look and name for Google Web Fonts

| More

Google Web Fonts: A new look and name for Google Web Fonts

This week, Google Web Fonts got a simpler, cleaner look that makes searching and accessing your fonts easier than ever. And in the spirit of simplicity, today Google Web Fonts is now just “Google Fonts.” It’s still the same great collection of free fonts you know and love, but with a new name.


You can get started with Google Fonts here: www.google.com/fonts

Posted by Ajay Surie, Product Manager
URL: http://googlewebfonts.blogspot.com/2013/04/a-new-look-and-name-for-google-web-fonts.html

Thursday, April 11, 2013

[Gd] Dev Channel Update for Chrome OS

| More

Chrome Releases: Dev Channel Update for Chrome OS

The Dev channel has been updated to 27.0.1453.46 (Platform version: 3912.23.0) for all Chromebooks. This build contains a number of bug fixes and feature enhancements.

Release Highlights:

  • Updated Pepper Flash to version 11.7.700.169-r2, resolving some issues with video playback quality
  • Volume bubble no longer displayed on login (225531)
  • Fixes for network connection error notifications (224676)
  • Updated Chrome Office Viewer extension

Known Issues:
  • On Samsung Chromebooks, HTML5 video playback is not always smooth. (225563)
  • Fix to issue that blocked returning to the current folder when viewing photos (223494)
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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

Danielle Drew
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/04/dev-channel-update-for-chrome-os_10.html

[Gd] Chrome Beta for Android Update

| More

Chrome Releases: Chrome Beta for Android Update

The Chrome Team is happy to announce the promotion of Chrome 27 to the Beta channel for Android. Chrome 27.0.1453.49 contains a number of great new updates including:
  • Fullscreen on phones - Scroll down the page and the toolbar will disappear.
  • Simpler searching - Searching from the omnibox will keep your search query visible in the omnibox, making it easier to edit, and show more on your search result page.
  • Client-side certificate support - You can now access sites that require you to use a certificate and Chrome will allow you to select an installed certificate
  • Tab history on tablets - Long press the browser back button to view your tab history
Known Issues:
  • Noticeable lag in text entry on some text fields
  • chrome://history sometimes show duplicate items
  • Opening tabs is sometimes slow
  • Pages may flicker sometimes, especially during navigation 
A partial list of changes in this build is available in the SVN revision log. 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.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/04/chrome-beta-for-android-update.html

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Stable channel has been updated to 26.0.1410.65 only for Mac. This release fixes WebGL bug which got regressed in last stable build. 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
URL: http://googlechromereleases.blogspot.com/2013/04/stable-channel-update_10.html

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 27.0.1453.47 for Windows, Mac, Linux, and Chrome Frame. 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.

Karen Grunberg
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/04/beta-channel-update.html

Wednesday, April 10, 2013

[Gd] Introducing "x-default hreflang" for international landing pages

| More

Official Google Webmaster Central Blog: Introducing "x-default hreflang" for international landing pages

Webmaster Level: All

The homepages of multinational and multilingual websites are sometimes configured to point visitors to localized pages, either via redirects or by changing the content to reflect the user’s language. Today we’ll introduce a new rel-alternate-hreflang annotation that the webmaster can use to specify such homepages that is supported by both Google and Yandex.

To see this in action, let’s look at an example. The website example.com has content that targets users around the world as follows:

Map of the world illustrating which hreflang code to use for which locale

In this case, the webmaster can annotate this cluster of pages using rel-alternate-hreflang using Sitemaps or using HTML link tags like this:



<link rel="alternate" href="http://example.com/en-gb" hreflang="en-gb" />
<link rel="alternate" href="http://example.com/en-us" hreflang="en-us" />
<link rel="alternate" href="http://example.com/en-au" hreflang="en-au" />
<link rel="alternate" href="http://example.com/" hreflang="x-default" />

The new x-default hreflang attribute value signals to our algorithms that this page doesn’t target any specific language or locale and is the default page when no other page is better suited. For example, it would be the page our algorithms try to show French-speaking searchers worldwide or English-speaking searchers on google.ca.

The same annotation applies for homepages that dynamically alter their contents based on a user’s perceived geolocation or the Accept-Language headers. The x-default hreflang value signals to our algorithms that such a page doesn’t target a specific language or locale.

As always, if you have any questions or feedback, please tell us in the Internationalization Webmaster Help Forum.

Posted by Pierre Far, Webmaster Trends Analyst

URL: http://googlewebmastercentral.blogspot.com/2013/04/x-default-hreflang-for-international-pages.html

[Gd] App Engine 1.7.7 Released

| More

Google App Engine Blog: App Engine 1.7.7 Released


3 weeks following our last release, the App Engine team is happy to announce 1.7.7.  We plan to deliver our Google I/O release next month.  




Outbound sockets moved to Preview

Outbound sockets is now in preview in this release for Java and Python.  With outbound sockets, billing-enabled App Engine applications can now make outbound connections with TCP or UDP sockets.  This allows developers to build applications that weren’t previously possible on App Engine, such as IMAP or DNS clients.




In the Python runtime, we’ve added support for the Python SSL Library, so you can now open secure connections to remote services such as Apple’s Push Notification service. Similarly, Java developers can now use the javax.net.ssl package to make outbound SSL connections.




Java 7 runtime upgraded to General Availability


The App Engine team is committed to quickly releasing features to General Availability.  You may recall we announced that the Java 7 runtime was in preview just 2 months ago.  Since then we have seen 200% adoption week over week, and today are happy to announce the General Availability of the runtime.  




In order to help developers move over, all app deployments initiated using the new 1.7.7 SDK will use Java 7 unless you explicitly opt out with a command line flag.  In the near future, we plan to automatically update all existing Java 6 applications to Java 7.  Most applications shouldn’t be affected by this change, but we encourage you to start testing your application in advance.  For more compatibility information, we suggest that you check out the Java SE 7 and JDK 7 Compatibility notes.




Google App Engine Maven Plugin


The Google App Engine Maven plugin has been updated to support new goals: now you can directly enhance Datanucleus classes, and generate Google Cloud Endpoints service discovery and client libraries.




Improving the developer experience - goodbye $2.10!


We’re happy to announce that billing-enabled applications will no longer be required to spend a minimum of $2.10 per week. This means that you can enable billing for a free tier application and continue running within the free tier without concern that a spike in traffic will terminate serving (note that you can always specify a daily dollar budget). The minimum spend was originally intended to prevent abuse and ensure that we can offer a stable, reliable system with a free tier.  We have determined that we can continue to support the free tier, without relying on the minimum spend.  So, goodbye $2.10!




Cloud SDK Preview


In our continuing effort to make developers’ lives easier, we are happy to share with you a preview release of the Google Cloud SDK which includes everything from the App Engine SDKs for Java, Python or Go as well as all the tools needed to target Google Compute Engine, Google Cloud SQL, Google Cloud Storage and Google BigQuery in one easy-to-use package.  Please try it out; we are eager to hear your feedback.




A note on reliability improvements


A key benefit of running on a managed service like App Engine is the changes that occur behind the scenes that automatically improve the performance of your applications.  In just the past two months, we’ve made many such improvements:



  • Faster and more consistent deployments.  Many customers are seeing up to 10x reductions in time to deploy a new application version.



  • We have fully deployed an entirely new scheduler system which autoscales applications more smoothly and efficiently.





  • Admin console dashboard charts and current load/error reports have moved to a new, more reliable backend



  • The release version of App Engine is now visible in the Admin Console and in request logs



  • Several stability and scheduling improvements to Task Queue






The complete list of features and bug fixes for 1.7.7 can be found in our release notes. For App Engine coding questions and answers check us out on Stack Overflow, and for general discussion and feedback, find us on our Google Group.






- Posted by Chris Ramsdale, Product Manager









URL: http://googleappengine.blogspot.com/2013/04/app-engine-177-released.html

[Gd] Chrome for iOS Update

| More

Chrome Releases: Chrome for iOS Update

The Chrome Team is happy to announce Chrome 26 for iPhone and iPad. Chrome 26.0.1410.50 contains a number of updates including:
  • Fullscreen
  • Support for Google Cloud Print, Air Print
  • Performance and stability improvements
The update will be rolling out in the App Store over the next few hours. Known issues are available on the Chrome support site. If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/04/chrome-for-ios-update.html

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Stable channel has been updated to 26.0.1410.63 for Mac and Linux; 26.0.1410.64 for Windows and Chrome Frame. This release contains stability improvements, and a new version of Adobe Flash.  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
URL: http://googlechromereleases.blogspot.com/2013/04/stable-channel-update.html

Tuesday, April 9, 2013

[Gd] New Look, New Purchase Flow in Google Play

| More

Android Developers Blog: New Look, New Purchase Flow in Google Play

Posted by Purnima Kochikar, Director of Business Development, Games & Applications

Today we announced that a new version of the Google Play Store app is rolling out worldwide to Android phones and tablets. This new app brings a redesigned UI that’s easier to use and showcases more great content for users. For developers, the new app offers more ways for your app to get noticed, as well as a new, simpler purchase flow.





The new UI is simple and easier to browse. Collections are front and center on the homepage, helping users discover great content through recommendations and curated lists. Items in collections are now presented as cards, with a larger area for your app’s graphics and a larger touch target for users. Overall, the homepage surfaces more apps than before and highlights them more effectively right on the page.





Most important for apps that sell in-app products, the new UI offers a dramatically simplified, dialog-based purchase flow that lets users buy your products without leaving the context of the app. Your app remains active and visible behind the purchase dialogs. When the purchase is complete, users return directly to the place they left, without your app having to reconstruct its state. It’s especially powerful when combined with In-app Billing v3, providing a faster and more reliable purchase flow.



All of these changes build on the core features of Google Play. Our editorial team will continue to look for exemplary apps to showcase in Editors’ Choice and other collections, and our familiar top lists will continue to track the market performance of your app on an ongoing basis.



Watch for the new Play Store app (version 4.0.25) coming to your devices soon. The rollout has already started and we expect all devices running Android 2.2 or higher to have received the update over the next few weeks.

URL: http://android-developers.blogspot.com/2013/04/new-look-new-purchase-flow-in-google.html

[Gd] Dev Channel Update

| More

Chrome Releases: Dev Channel Update

The Dev channel has been updated to 28.0.1469.0 for Mac, Windows, and Chrome Frame

This build addresses some known regressions and stability issues. 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.

Anthony Laforge
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/04/dev-channel-update_8.html

[Gd] Chrome OS Stable Channel Update

| More

Chrome Releases: Chrome OS Stable Channel Update



The Stable channel has been updated to 26.0.1410.57 (Platform version: 3701.81.0) for all Chrome OS devices. This build contains a number of bug fixes and security improvements. Machines will be receiving updates over the next several days.

Release highlights:
  • Pepper Flash updated to 11.6.602.180
  • GTalk plugin updated to 3.14.17
  • Bluetooth UI improvements in the Status Area to ease connecting and managing Bluetooth devices
  • Updated wallpaper picker UI (New style, All category)
  • Added Widevine Content Decryption Module (CDM) on Intel platforms
  • Significant video performance improvements in Widevine CDM on ARM platforms.
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.
    • [189250] High CVE-2013-0927: Unsafe config option loading in Pango. Credit to Pinkie Pie.
Known Issues:

  • In some situations, the screen may dim while in a hangout.
    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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

    Ben Henry
    Google Chrome

    URL: http://googlechromereleases.blogspot.com/2013/04/chrome-os-stable-channel-update.html

    [Gd] 5 common mistakes with rel=canonical

    | More

    Official Google Webmaster Central Blog: 5 common mistakes with rel=canonical

    Webmaster Level: Intermediate to Advanced Including a rel=canonical link in your webpage is a strong hint to search engines your preferred version to index among duplicate pages on the web. It’s supported by several search engines, including Yahoo!, Bing, and Google. The rel=canonical link consolidates indexing properties from the duplicates, like their inbound links, as well as specifies which URL you’d like displayed in search results. However, rel=canonical can be a bit tricky because it’s not very obvious when there’s a misconfiguration.
    While the webmaster sees the “red velvet” page on the left in their browser, search engines notice on the webmaster’s unintended “blue velvet” rel=canonical on the right.
    We recommend the following best practices for using rel=canonical:
    • A large portion of the duplicate page’s content should be present on the canonical version.
    • One test is to imagine you don’t understand the language of the content—if you placed the duplicate side-by-side with the canonical, does a very large percentage of the words of the duplicate page appear on the canonical page? If you need to speak the language to understand that the pages are similar; for example, if they’re only topically similar but not extremely close in exact words, the canonical designation might be disregarded by search engines.
    • Double-check that your rel=canonical target exists (it’s not an error or “soft 404”)
    • Verify the rel=canonical target doesn’t contain a noindex robots meta tag
    • Make sure you’d prefer the rel=canonical URL to be displayed in search results (rather than the duplicate URL)
    • Include the rel=canonical link in either the <head> of the page or the HTTP header
    • Specify no more than one rel=canonical for a page. When more than one is specified, all rel=canonicals will be ignored.
    Mistake 1: rel=canonical to the first page of a paginated seriesImagine that you have an article that spans several pages:
    • example.com/article?story=cupcake-news&page=1
    • example.com/article?story=cupcake-news&page=2
    • and so on
    Specifying a rel=canonical from page 2 (or any later page) to page 1 is not correct use of rel=canonical, as these are not duplicate pages. Using rel=canonical in this instance would result in the content on pages 2 and beyond not being indexed at all.
    Good content (e.g., “cookies are superior nutrition” and “to vegetables”) is lost when specifying rel=canonical from component pages to the first page of a series.
    In cases of paginated content, we recommend either a rel=canonical from component pages to a single-page version of the article, or to use rel=”prev” and rel=”next” pagination markup.
    rel=canonical from component pages to the view-all page
    If rel=canonical to a view-all page isn’t designated, paginated content can use rel=”prev” and rel=”next” markup.
    Mistake 2: Absolute URLs mistakenly written as relative URLs
    The <link> tag, like many HTML tags, accepts both relative and absolute URLs. Relative URLs include a path “relative” to the current page. For example, “images/cupcake.png” means “from the current directory go to the “images” subdirectory, then to cupcake.png.” Absolute URLs specify the full path—including the scheme like http://. Specifying <link rel=canonical href=“example.com/cupcake.html” /> (a relative URL since there’s no “http://”) implies that the desired canonical URL is http://example.com/example.com/cupcake.html even though that is almost certainly not what was intended. In these cases, our algorithms may ignore the specified rel=canonical. Ultimately this means that whatever you had hoped to accomplish with this rel=canonical will not come to fruition. Mistake 3: Unintended or multiple declarations of rel=canonicalOccasionally, we see rel=canonical designations that we believe are unintentional. In very rare circumstances we see simple typos, but more commonly a busy webmaster copies a page template without thinking to change the target of the rel=canonical. Now the site owner’s pages specify a rel=canonical to the template author’s site.
    If you use a template, check that you didn’t also copy the rel=canonical specification.
    Another issue is when pages include multiple rel=canonical links to different URLs. This happens frequently in conjunction with SEO plugins that often insert a default rel=canonical link, possibly unbeknownst to the webmaster who installed the plugin. In cases of multiple declarations of rel=canonical, Google will likely ignore all the rel=canonical hints. Any benefit that a legitimate rel=canonical might have offered will be lost. In both these types of cases, double-checking the page’s source code will help correct the issue. Be sure to check the entire <head> section as the rel=canonical links may be spread apart.
    Check the behavior of plugins by looking at the page’s source code.
    Mistake 4: Category or landing page specifies rel=canonical to a featured articleLet’s say you run a site about desserts. Your dessert site has useful category pages like “pastry” and “gelato.” Each day the category pages feature a unique article. For instance, your pastry landing page might feature “red velvet cupcakes.” Because the “pastry” category page has nearly all the same content as the “red velvet cupcake” page, you add a rel=canonical from the category page to the featured individual article. If we were to accept this rel=canonical, then your pastry category page would not appear in search results. That’s because the rel=canonical signals that you would prefer search engines display the canonical URL in place of the duplicate. However, if you want users to be able to find both the category page and featured article, it’s best to only have a self-referential rel=canonical on the category page, or none at all.
    Remember that the canonical designation also implies the preferred display URL. Avoid adding a rel=canonical from a category or landing page to a featured article.
    Mistake 5: rel=canonical in the <body>The rel=canonical link tag should only appear in the <head> of an HTML document. Additionally, to avoid HTML parsing issues, it’s good to include the rel=canonical as early as possible in the <head>. When we encounter a rel=canonical designation in the <body>, it’s disregarded. This is an easy mistake to correct. Simply double-check that your rel=canonical links are always in the <head> of your page, and as early as possible if you can.
    rel=canonical designations in the <head> are processed, not the <body>.
    ConclusionTo create valuable rel=canonical designations:
    • Verify that most of the main text content of a duplicate page also appears in the canonical page.
    • Check that rel=canonical is only specified once (if at all) and in the <head> of the page.
    • Check that rel=canonical points to an existent URL with good content (i.e., not a 404, or worse, a soft 404).
    • Avoid specifying rel=canonical from landing or category pages to featured articles as that will make the featured article the preferred URL in search results.
    And, as always, please ask any questions in our Webmaster Help forum. Written by Allan Scott, Software Engineer, Indexing Team
    URL: http://googlewebmastercentral.blogspot.com/2013/04/5-common-mistakes-with-relcanonical.html