Extended Stable Updates for Desktop

The Extended Stable channel has been updated to 130.0.6723.152 for Windows and Mac which will roll out over the coming days/weeks.


A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Daniel Yip
Google Chrome

Now generally available: configure third-party apps by select API scopes

What’s changing 

Earlier this year, we launched the ability to configure third-party apps by select API scopes to open beta. Beginning today, this feature is now generally available. 


This update gives admins more granular control. They can limit third-party app access to specific OAuth 2.0 scopes for Google APIs, like Drive or Gmail. This prevents apps from gaining additional access without admin consent, even if they request new API scopes in the future. This helps ensure data access is restricted to only what admins deem necessary.



Getting started


Rollout pace


Availability

  • Available to all Google Workspace customers, as well as Cloud Identity Free and Premium customers


Resources


New beta that supports running Google Drive on Arm-compatible Windows PCs now available

What’s changing

We're excited to announce beta support for Drive for desktop on Windows 11 devices powered by Snapdragon processors. Compiled natively for ARM64, this release enables users to easily sync and store files online from Windows PCs powered by Snapdragon. 


To opt-in to the beta, download and install the beta version of Google Drive for desktop on Arm-compatible Windows 11 device powered by Snapdragon. If you wish to opt-out at any time, disconnect your account and then uninstall the application. 


Getting started 

  • Admins: There is no admin control for this feature. 
  • End users:
    • The beta version of Google Drive for desktop can only be installed on devices running Windows 11 and requires Microsoft WebView2, which is typically included with Windows 11. If it is missing or was previously removed, our installer will recommend you download and install it. 
    • Note: This is a beta version and may contain bugs. It should be used with non-production data only. Alternatively, ensure that your data is backed up separately. 
    • Should you encounter any issues, please submit feedback through the application. Kindly include logs to facilitate troubleshooting and assist us in improving the application. 

Availability 

  • Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts 

Resources 

Tech on the Toilet: Driving Software Excellence, One Bathroom Break at a Time

By Kanu Tewary and Andrew Trenk


Tech on the Toilet (TotT) is a weekly one-page publication about software development that is posted in bathrooms in Google offices worldwide.  At Google, TotT is a trusted source for high quality technical content and software engineering best practices. TotT episodes relevant outside Google are posted to this blog.


We have been posting TotT to this blog since 2007. We're excited to announce that Testing on the Toilet has been renamed to Tech on the Toilet. TotT originally covered only software testing topics, but for many years has been covering any topics relevant to software development, such as coding practices, machine learning, web development, and more.


A Cultural Institution


TotT is a grassroots effort with a mission to deliver easily-digestable one-pagers on software development to engineers in the most unexpected of places: bathroom stalls! But TotT is more than just bathroom reading -- it's a movement. Driven by a team of 20-percent volunteers, TotT empowers Google employees to learn and grow, fostering a culture of excellence within the Google engineering community.



Photo of TotT posted in a bathroom stallPhoto of TotT posted in a bathroom stall

Photos of TotT posted in bathroom stalls at Google.


Anyone at Google can author a TotT episode (regardless of tenure or seniority). Each episode is carefully curated and edited to provide concise, actionable, authoritative information about software best practices and developer tools. After an episode is published, it is posted to Google bathrooms around the world, and is also available to read online internally at Google. TotT episodes often become a canonical source for helping far-flung teams standardize their software development tools and practices.  


Because Every Superhero Has An Origin Story 

TotT began as a bottom-up approach to drive a culture change. The year was 2006 and Google was experiencing rapid growth and huge challenges: there were many costly bugs and rolled-back releases. A small group of engineers, members of the so-called Testing Grouplet, passionate about testing, brainstormed about how to instill a culture of software testing at Google. In a moment of levity, someone suggested posting flyers in restrooms (since people have time to read there, clearly!). The Testing Grouplet named their new publication Testing on the Toilet. TotT’s red lightbub, green lightbulb logo–displayed at the top of the page of each printed flyer–was adapted from the Testing Grouplet’s logo.   

The TotT logo

The TotT logo.

The first TotT episode, a simple code example with a suggested improvement, was written by an engineer at Google headquarters in Mountain View, and posted by a volunteer in Google bathrooms in London. Soon other engineers wrote episodes, and an army of volunteers started posting those episodes at their sites. Hundreds of engineers started encountering TotT episodes.

The initial response was a mix of surprise and intrigue, with some engineers even expressing outrage at the "violation" of their bathroom sanctuary. However, the majority of feedback was positive, with many appreciating the readily accessible knowledge. Learn more about the history of TotT in this blog post by one of the original members of the Testing Grouplet.  

Trusted, Concise, Actionable

TotT has become an authoritative source for software development best practices at Google. Many episodes, like the following popular episodes at Google, are cited hundreds of times in code reviews and other internal documents: 

A 2019 research paper presented at the International Conference of Software Engineering even analyzed the impact of TotT episodes on the adoption of internal tools and infrastructure, demonstrating its effectiveness in driving positive change.

TotT has inspired various other publications at Google, like Learning on the Loo: non-technical articles to improve efficiency, reduce stress and improve work satisfaction. Other companies have been inspired to create their own bathroom publications, thanks to TotT. So the next time you find yourself reading a TotT episode, take a moment to appreciate its humble bathroom beginnings. After all, where better to ponder the mysteries of the code than in a place of quiet contemplation?

Crawling December: The how and why of Googlebot crawling

You may have heard that Google Search needs to do a bit of work before a web page can show up in Google Search results. One of these steps is called crawling. Crawling for Google Search is done by Googlebot, a program running on Google servers that retrieves a URL and handles things like network errors, redirects, and other small complications that it might encounter as it works its way through the web. But there are a few details that aren't often talked about. Each week this month we're going to explore some of those details as they may have a significant effect on how your sites are crawled.

Now generally available: Policy visualization across Google Docs, Sheets, Slides, Vids and Drive

What’s changing 

Earlier this year, we introduced a beta for policy visualization across Google Docs, Sheets, Slides, and Drive. Today, we’re excited to announce this is now generally available, and as a result, users who are interacting with policy-protected content, such as those with data loss prevention (DLP) rules or trust rules, will now be informed about what actions are prevented by those policies. 

For example, if a user is interacting with a document affected by DLP-enforced information rights management (IRM) and a trust rule, they will see a shield icon and side panel that informs them of the restricted actions. 

Policy visualization across Google Docs, Sheets, Slides, Vids and Drive



Who’s impacted

End users 


Why it matters 

With this update, users will be made aware of which actions they are taking that are disabled on a document, spreadsheet, slides or file due to data protection controls. 


Getting started

  • Admins: There is no admin control for this feature. 
  • End users: 
    • Any user will be able to see policy visualization if relevant restrictions apply to them. Security limitations can be applied by owners of a document, shared drive policies, or admin policies. 
    • A shield icon will automatically appear when security controls are present. Users can open the side panel to view all restrictions, either using the shield icon or by going to File > Security limitations. 
    • Visit the Help Center to learn more about Policy Visualization and the policies themselves: 

Rollout pace 

Availability

  • Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts

Resources