Updated options to better view Google Calendar on large monitors

To provide users with more control over their viewing experience, we’re updating information density options for the calendar grid. These updates allow users to customize how calendar events scale on their screens to accommodate various monitor sizes and personal preferences.

The available information density options now include:

  • Responsive to your screen: Your calendar dynamically scales and enlarges events to fill larger monitors, which makes events easier to read.
  • Comfortable: Your calendar keeps the standard layout with traditional spacing, regardless of your screen size.
  • Compact: Your calendar shows a denser view with tighter spacing, which allows you to see more events at once.

New options in Calendar information density to adjust for large monitors

Getting started

  • Admins: There is no admin control for this feature.
  • End users: Change your density settings from the Appearance settings menu in Calendar on the web. Visit the Help Center to learn more.

Rollout pace

  • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on July 29, 2026
  • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on August 10, 2026

Availability

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

Resources

Delivering safer, age-appropriate experiences on Google Play

Posted by Paul Feng, VP of Product Management, Google Play




Providing a safe online experience and protecting users from harm is a top priority at Google Play. We take this responsibility seriously and have been investing continuously to offer baseline protections on our platform while also empowering parents with the tools they need to make decisions for their families. Importantly, we also want to empower Play developers with the capabilities to deliver age-appropriate experiences based on their app's content.

To support this, today, we are taking another big step in our ongoing partnership with parents and developers by announcing the expansion of the Google Play Age Signals API to all Play developers globally. Building on current availability in Brazil, we will expand this experience first to users in Australia and Canada by mid-August, with a full global rollout to all users later this year.

Empowering developers to create age-appropriate experiences

The Play Age Signals API is a privacy-preserving tool that puts parents in the driver's seat allowing them to share their child's age range (e.g. 16-17) directly with apps. It also enables adults to easily share their age when prompted by the app developer. In turn, developers receive the signals they need to tailor their own in-app safety experiences and content for users in an age-appropriate way.

We want to give developers the ability to choose the right protections for the nature of their app. A weather app, for example, shouldn't need the same safety settings as entertainment or media apps. Rather than enforcing one-size-fits-all rules, we give developers the flexibility to choose how they integrate safety signals. With this reliable signal, you retain complete agency to tailor your app's content, features, and settings to match your audience.

Users have a choice to share their age range in a privacy-friendly way

Simplifying controls for parents

Parents shouldn't have to manage complex safety settings across dozens of different apps to keep their children safe. The Play Age Signals API simplifies this by putting age-sharing controls in one place, directly inside the Google Family Link app. Parents have a choice to share their child’s age range, and if they choose to share, all Play apps that use Play Age Signals API can receive age signals. This lets children jump straight into age-appropriate content without parents having to manually configure settings inside these apps. Age ranges are never shared by default, and parents can update or turn off these settings at any time.

Centralized and easy way to manage age sharing settings for parents via Family Link App

Building on our broader safety tools

The Play Age Signals API builds upon a strong foundation of established safety features and strict policies we have long enforced on Google Play. Today, we already mandate that apps designed for families meet rigorous safety standards, and we continuously review and scan applications to ensure they are safe for children. For developers, we also offer built-in tools like Restrict Minor Access in the Play Console to help them manage who can discover their apps. For parents, Google Family Link remains a trusted, central dashboard where they can manage screen-time limits, PIN-based content filters, and app download approvals.

Expanding the Play Age Signals API globally adds a powerful new tool to our existing safety suite, helping parents and developers work together to make Google Play an even safer, more trustworthy place for families.


Beta Channel Update for ChromeOS / ChromeOS Flex

The Beta channel is being updated to OS version 16733.33.0 (Browser version 151.0.7922.56) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:



  1. File a bug

  2. Visit our ChromeOS communities

    1. General: Chromebook Help Community

    2. Beta Specific: ChromeOS Beta Help Community

  3. Report an issue or send feedback on Chrome

  4. Interested in switching channels? Find out how.


Andy Wu

Google ChromeOS

Long Term Support Channel Update for ChromeOS

A new LTS-144  version 144.0.7559.258(Platform Version: 16503.91.0), is being rolled out for most ChromeOS devices. 

This version includes selected security fixes including:


515429352 High CVE-2026-11669 Integer overflow in Media on ChromeOS


495939973 Critical CVE-2026-8513 Use after free in Input


511742228 High CVE-2026-9979 Insufficient validation of untrusted input in Input


513774197 High CVE-2026-10982 Use after free in WebXR


517644287 High CVE-2026-11693 Inappropriate implementation in Plugins


517705966 High CVE-2026-11694 Use after free in ServiceWorker


513731890 High CVE-2026-11660 Insufficient validation of untrusted input in New Tab Page


518105731 High CVE-2026-11697 Insufficient validation of untrusted input in UI


517607902 High CVE-2026-11692 Use after free in Read Anything


515469283 High CVE-2026-11670 Use after free in PDF


517168239 High CVE-2026-11646 Use after free in ViewTransitions


517129549 High CVE-2026-11683 Use after free in WebCodecs


517486004 High CVE-2026-11689 Insufficient validation of untrusted input in Passwords


503929476 High CVE-2026-9952 Use after free in WebAudio


511736002 High CVE-2026-11651 Use after free in Network


513762354 High CVE-2026-10981 Insufficient validation of untrusted input in Codecs


517103584 High CVE-2026-11682 Insufficient validation of untrusted input in Views


516910450 High CVE-2026-11674 Use after free in Guest View


515465685 High CVE-2026-10988 Use after free in Views


513773313 High CVE-2026-11662 Type Confusion in Bindings


533446300 Critical CVE-2026-15901 Use after free in Network


513028160 High CVE-2026-9986 Insufficient validation of untrusted input in OptimizationGuide


497047552 High CVE-2026-7357 Use after free in GPU


513019760 High CVE-2026-9985 Insufficient validation of untrusted input in Media


518007484 Critical CVE-2026-15765 Use after free in Ozone


417052041 Medium CVE-2026-13860 Incorrect security UI in Autofill


527406824 High CVE-2026-15133 Use after free in InterestGroups


505815080 Critical CVE-2026-10888 Use after free in Cast Streaming


524045160 Critical CVE-2026-15129 Use after free in Views


Release notes for LTS-144 can be found here 

Want to know more about Long-term Support? Click here

Andy Wu

Google Chrome OS

Extended Stable Updates for Desktop

 The Extended Stable channel has been updated to 150.0.7871.212 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.

Krishna Govind
Google Chrome