Third-party smart chip resource creation now available in Google Docs

What’s changing 

Last year, we introduced the ability to pull rich data from apps directly into Google Docs with third-party smart chips. Today, we’re taking this a step further by enabling third-party partners, such as Lucidspark, Lucidchart, and Zoho Projects, to create smart chips or resources like tasks or flowcharts that end users can add and edit in their Google Docs. 

To access third-party smart chips, an admin or user must first install a partner’s add-on from the Google Workspace Marketplace and then users can search for items to create using the @ menu in Docs. After the item is selected, a creation form will appear that includes text input fields relevant to the type of resource being generated. Once the third-party smart chip is inserted, users can hover over it and view a preview of the content.
Seamless linking between Zoho Projects and Google Docs

Who’s impacted 

Admins, end users and developers (partners) 


Why you’d use it 

This feature expands upon your ability to add, view and engage with critical information from third party apps by letting you create third-party resource content. 


Additional details 

Other third-party partners, such as Jira & Confluence, plan to add resource creation to their existing third-party smart chip add-ons in the Google Workspace Marketplace later this year. 


Getting started 

Rollout pace

Availability 

Chrome Dev for Android Update

Hi everyone! We've just released Chrome Dev 130 (130.0.6669.0) for Android. It's now available on Google Play.

You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.

If you find a new issue, please let us know by filing a bug.

Erhu Akpobaro
Google Chrome

Google and Minister Judith Collins co-host “an evening of AI” at Parliament

Government officials, business leaders and Google reps discussed AI’s potential to build a brighter future for New Zealand

Aug 22 - Google has reaffirmed its passion to support the New Zealand government in harnessing the power of AI to build a brighter future for the country. This was expressed during high-level discussions held yesterday in Wellington with Honourable Judith Collins, Minister for Digitising Government, and other key government officials.

At the event co-hosted by Minister Collins and Google New Zealand, a delegation of Google representatives, led by Country Director Caroline Rainsford, and including Urs Hölzle, one of Google’s earliest employees, shared their insights on AI's potential to drive economic growth, innovation, and societal progress. In attendance were key government figures including Paul James (Government Chief Digital Officer). 

Google’s visit to Parliament aimed to showcase the exciting potential of AI to bring positive change to New Zealand. As a leader in AI innovation, Google also highlighted the company’s readiness to support this journey, while stressing the need for proactive engagement from government agencies to fully realise these opportunities.

Caroline Rainsford addresses the crowd at last night's Hui

Caroline Rainsford, Country Director of Google New Zealand, says: "The energy at Parliament House was palpable. There was definitely a shared excitement about AI's potential to transform New Zealand. From revolutionising healthcare to personalising education, the possibilities are immense.”

The discussions also highlighted the importance of smart regulations and collaborative efforts between the public and private sectors, to ensure the responsible and beneficial development of AI in New Zealand.

Rainsford adds: “Minister Collin’s optimistic approach to AI resonates with our vision. With our strong local presence, AI expertise, Cloud tools, and more, Google is ready to support the government’s vision for a digital New Zealand. We’re confident that we can help the country realise its AI aspirations with action and proactive engagement from government agencies."

Posted by Caroline Rainsford, Country Director of Google New Zealand

Chrome for Android Update

Hi, everyone! We've just released Chrome 128 (128.0.6613.88) for Android . It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Android releases contain the same security fixes as their corresponding Desktop (Windows & Mac: 128.0.6613.84/85 and Linux:128.0.6613.84) unless otherwise noted.


Harry Souders
Google Chrome

Chrome Stable for iOS Update

Hi everyone! We've just released Chrome Stable 128 (128.0.6613.92) for iOS; it'll become available on App Store in the next few hours.

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Harry Souders
Google Chrome

Dev Channel Update for ChromeOS / ChromeOS Flex

The Dev channel is being updated to OS version: 16002.2.0, Browser version: 129.0.6668.0 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.

Matt Nelson,

Google ChromeOS

Google Meet increases ultra-low latency live streaming support to 100,000 viewers in distributed audiences

What’s changing

For select Google Workspace editions*, we’re pleased to announce that the Google Meet ultra-low latency viewing experience for live streamed meetings will now support up to 100,000 viewers. This gives organizations the flexibility to reach a wider audience with improved user experience at lower bandwidth consumption. In order to receive the ultra-low latency experience, no more than 25,000 viewers can be connected to a single regional data center at a time. 


Who’s impacted 

Admins and end users 


Why it’s important 

Live streaming is a critical tool for large audiences, such as town-halls or keynote events. Increasing support for the low-latency live streaming experience from 25,000 viewers to 100,000 users helps our customers reach a wider audience, while their users benefit from several functional and quality improvements, such as:

  • A virtually lag-free experience
  • Significantly increased speaker video resolution (up to 720p per speaker)
  • Shared content and presentations shown up to 2880x1800
  • Improved automatic camera cuts that focus on the most relevant speakers & content 
  • Audience interaction through emoji reactions, polls and Q&A, and more.


Additional details

Enterprise Content Delivery Network (eCDN) for Google Meet
If large groups of your audience are connecting from a single network location or a shared gateway, you may benefit from using eCDN for Meet to get full media quality with substantial network bandwidth savings. For more information on eCDN, see this post on the Workspace Updates blog and visit our Help Center.    


Viewers can now join ultra-low latency live streams from Google Meet room hardware
The Google Meet ultra-low latency viewing experience for live streamed meetings is now available also from Google Meet room hardware. Live streaming is a critical tool for large audiences, such as town-halls or keynote events. Support for room hardware means that users can join and watch live streams together in smaller or larger groups. To view a live stream via Google Meet hardware, invite the room to a view-only calendar event granted that your host has allowed guests to modify events. When the event is about to start, the live stream will be visible with its name as an upcoming event in the room agenda. Join the live stream by tapping it on the touch screen.


Meeting hosts and meeting organizers can invite rooms directly in view-only calendar events — visit the Help Center to learn more about live streaming a video meeting. If the calendar event is locked for editing, individual users can also duplicate the event and create their own view-only copy with the rooms they want to add as viewing locations. Visit the Help Center to learn more about viewing a live stream.


Getting started

Rollout pace


Availability

  • Available to Google Workspace Enterprise Plus, Education Plus, and Enterprise Essentials Plus customers*

*Note: The ultra-low latency live streaming experience is rolling out at a slower pace for some customers. Once you receive the experience, you’ll be able to take advantage of these updates.


Resources


Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 129 (129.0.6668.9) for Android. It's now available on Google Play.

You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.

If you find a new issue, please let us know by filing a bug.

Krishna Govind
Google Chrome

Stable Channel Update for Desktop

The Chrome team is delighted to announce the promotion of Chrome 128 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.


Chrome 128.0.6613.84 (Linux) 128.0.6613.84/.85( Windows, Mac) contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 126.

Chrome 128.0.6613.84( Windows, Mac) has been pushed to extended stable channel as well

 Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.


This update includes 38 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[$36000][358296941] High CVE-2024-7964: Use after free in Passwords. Reported by Anonymous on 2024-08-08

[$11000][356196918] High CVE-2024-7965: Inappropriate implementation in V8. Reported by TheDog on 2024-07-30

[$10000][355465305] High CVE-2024-7966: Out of bounds memory access in Skia. Reported by Renan Rios (@HyHy100) on 2024-07-25

[$7000][355731798] High CVE-2024-7967: Heap buffer overflow in Fonts. Reported by Tashita Software Security on 2024-07-27

[$1000][349253666] High CVE-2024-7968: Use after free in Autofill. Reported by Han Zheng (HexHive) on 2024-06-25

[TBD][351865302] High CVE-2024-7969: Type Confusion in V8. Reported by CFF of Topsec Alpha Team on 2024-07-09

[TBD][360700873] High CVE-2024-7971: Type confusion in V8. Reported by Microsoft Threat Intelligence Center (MSTIC), Microsoft Security Response Center (MSRC) on 2024-08-19

[$11000][345960102] Medium CVE-2024-7972: Inappropriate implementation in V8. Reported by Simon Gerst (intrigus-lgtm) on 2024-06-10

[$7000][345518608] Medium CVE-2024-7973: Heap buffer overflow in PDFium. Reported by soiax on 2024-06-06

[$3000][339141099] Medium CVE-2024-7974: Insufficient data validation in V8 API. Reported by bowu(@gocrashed) on 2024-05-07

[$3000][347588491] Medium CVE-2024-7975: Inappropriate implementation in Permissions. Reported by Thomas Orlita on 2024-06-16

[$2000][339654392] Medium CVE-2024-7976: Inappropriate implementation in FedCM. Reported by Alesandro Ortiz on 2024-05-10

[$1000][324770940] Medium CVE-2024-7977: Insufficient data validation in Installer. Reported by Kim Dong-uk (@justlikebono) on 2024-02-11

[$1000][40060358] Medium CVE-2024-7978: Insufficient policy enforcement in Data Transfer. Reported by NDevTK on 2022-07-21

[TBD][356064205] Medium CVE-2024-7979: Insufficient data validation in Installer. Reported by VulnNoob on 2024-07-29

[TBD][356328460] Medium CVE-2024-7980: Insufficient data validation in Installer. Reported by VulnNoob on 2024-07-30

[$1000][40067456] Low CVE-2024-7981: Inappropriate implementation in Views. Reported by Thomas Orlita on 2023-07-14

[$500][350256139] Low CVE-2024-8033: Inappropriate implementation in WebApp Installs. Reported by Lijo A.T on 2024-06-30

[$500][353858776] Low CVE-2024-8034: Inappropriate implementation in Custom Tabs. Reported by Bharat (mrnoob) on 2024-07-18

[TBD][40059470] Low CVE-2024-8035: Inappropriate implementation in Extensions. Reported by Microsoft on 2022-04-26


We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

Google is aware that an exploit for CVE-2024-7971 exists in the wild.


As usual, our ongoing internal security work was responsible for a wide range of fixes:

  • [361165957] Various fixes from internal audits, fuzzing and other initiatives


Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.


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.


Prudhvikumar Bommana
Google Chrome