Planet Chromium

March 26, 2020

Google Chrome Releases

Beta Channel Update for Desktop

The beta channel has been updated to 81.0.4044.83 for Windows, Mac, and, Linux.


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.



Prudhvikumar Bommana
Google Chrome

by Prudhvikumar Bommana (noreply@blogger.com) at March 26, 2020 12:47 PM

Dev Channel Update for Desktop

The Dev channel has been updated to 83.0.4093.3 for Windows, Mac, and Linux platforms.
A partial list of changes is available in the log. Interested in switching release channels? Find out how. 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.
Srinivas Sista Google Chrome

by Srinivas Sista (noreply@blogger.com) at March 26, 2020 11:54 AM

Chromium Blog

Chrome and Chrome OS release updates

Cross-posted from the Chrome Releases Blog

We previously paused upcoming releases for Chrome and Chrome OS. Today we’re sharing an update as we’re now resuming releases with an adjusted schedule:

  • M83 will be released three weeks earlier than previously planned and will include all M82 work as we cancelled the M82 release (all channels).
  • Our Canary, Dev and Beta channels have or will resume this week, with M83 moving to Dev, and M81 continuing in Beta.
  • Our Stable channel will resume release next week with security and critical fixes in M80, followed by the release of M81 the week of April 7, and M83 ~mid-May.
  • We will share a future update on the timing of the M84 branch and releases.

We continue to closely monitor that Chrome and Chrome OS are stable, secure, and work reliably. We’ll keep everyone informed of any changes on our schedule on our release blog and will share additional details on the schedule in the Chromium Developers group, as needed. You can also check our schedule page for specific dates for each milestone at any time.

Thanks everyone for the help and patience during this time.

Posted by the Chrome Release Team

by Chromium Blog (noreply@blogger.com) at March 26, 2020 10:01 AM

Google Chrome Releases

Chrome and Chrome OS release updates

We previously paused upcoming releases for Chrome and Chrome OS. Today we’re sharing an update as we’re now resuming releases with an adjusted schedule:
  • M83 will be released three weeks earlier than previously planned and will include all M82 work as we cancelled the M82 release (all channels).
  • Our Canary, Dev and Beta channels have or will resume this week, with M83 moving to Dev, and M81 continuing in Beta.
  • Our Stable channel will resume release next week with security and critical fixes in M80, followed by the release of M81 the week of April 7, and M83 ~mid-May.
  • We will share a future update on the timing of the M84 branch and releases.
We continue to closely monitor that Chrome and Chrome OS are stable, secure, and work reliably. We’ll keep everyone informed of any changes on our schedule on this blog and will share additional details on the schedule in the Chromium Developers group, as needed. You can also check our schedule page for specific dates for each milestone at any time.

Thanks everyone for the help and patience during this time.

Google Chrome 

by Josafat (noreply@blogger.com) at March 26, 2020 10:00 AM

March 25, 2020

Google Chrome Releases

Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 81 (81.0.4044.71) 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.

Ben Mason
Google Chrome

by Ben Mason (noreply@blogger.com) at March 25, 2020 06:54 AM

March 23, 2020

Google Chrome Releases

Dev Channel Update for Desktop

The Dev channel has been updated to 82.0.4085.12 for Windows, Mac, and Linux platforms.
A partial list of changes is available in the log. Interested in switching release channels? Find out how. 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.
Lakshmana Pamarthy Google Chrome

by Lakshmana Pamarthy (noreply@blogger.com) at March 23, 2020 12:21 PM

Stable Channel Update for Chrome OS

The Stable channel is being updated to 80.0.3987.158 (Platform version: 12739.105.0) for most Chrome OS devices. This build contains a number of bug fixes and security updates. Systems will be receiving updates over the next several days.

If you find new issues, please let us know by vising our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using 'Report an issue...' in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Daniel Gagnon
Google Chrome OS

by Daniel Gagnon (noreply@blogger.com) at March 23, 2020 12:17 PM

March 18, 2020

Google Chrome

Engineering Manager, Android Security and Privacy

Android is launching new features for Advanced Protection Program users to automatically protect them from malware.

by Roman Kirillov at March 18, 2020 01:00 PM

Google Chrome Releases

Chrome for Android Update

Hi, everyone! We've just released Chrome 80 (80.0.3987.149) for Android: it'll become available on Google Play over the next few weeks.

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.


Krishna Govind
Google Chrome

by Krishna Govind (noreply@blogger.com) at March 18, 2020 01:00 PM

Stable Channel Update for Desktop

The stable channel has been updated to 80.0.3987.149 for Windows, Mac, and Linux, which will roll out over the coming days/weeks.




A list of all changes is available in the log. Interested in switching release channels? Find out how. 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.

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 13 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

[$8500][1051748] High CVE-2020-6422: Use after free in WebGL. Reported by David Manouchehri on 2020-02-13
[$NA][1031142] High CVE-2020-6424: Use after free in media. Reported by Sergei Glazunov of Google Project Zero on 2019-12-05
[$NA][1031670] High CVE-2020-6425: Insufficient policy enforcement in extensions. Reported by Sergei Glazunov of Google Project Zero on 2019-12-06
[$TBD][1052647] High CVE-2020-6426: Inappropriate implementation in V8. Reported by Avihay Cohen @ SeraphicAlgorithms on 2020-02-16
[$TBD][1055788] High CVE-2020-6427: Use after free in audio. Reported by Man Yue Mo of Semmle Security Research Team on 2020-02-25
[$TBD][1057593] High CVE-2020-6428: Use after free in audio. Reported by Man Yue Mo of Semmle Security Research Team on 2020-03-02
[$TBD][1057627] High CVE-2020-6429: Use after free in audio. Reported by Man Yue Mo of Semmle Security Research Team on 2020-03-02
[$NA][1059349] High CVE-2019-20503: Out of bounds read in usersctplib. Reported by Natalie Silvanovich of Google Project Zero on 2020-03-06
[$TBD][1059686] High CVE-2020-6449: Use after free in audio. Reported by Man Yue Mo of Semmle Security Research Team on 2020-03-09

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.

As usual, our ongoing internal security work was responsible for a wide range of fixes:
  • [1057473] Various fixes from internal audits, fuzzing and other initiatives



Srinivas Sista
Google Chrome

by Srinivas Sista (noreply@blogger.com) at March 18, 2020 01:00 PM

Chromium Blog

Upcoming Chrome releases

Cross-posted from the Chrome Releases Blog

Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases. Our primary objectives are to ensure Chrome continues to be stable, secure, and work reliably for anyone who depends on them. We’ll continue to prioritize any updates related to security, which will be included in Chrome 80.


Please follow the Chrome Releases blog for updates.

Posted by the Chrome Release Team

by Chromium Blog (noreply@blogger.com) at March 18, 2020 11:01 AM

Google Chrome Releases

Upcoming Chrome and Chrome OS releases

Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases. Our primary objectives are to ensure they continue to be stable, secure, and work reliably for anyone who depends on them. We’ll continue to prioritize any updates related to security, which will be included in Chrome 80. Please, follow this blog for updates.

Google Chrome

by Josafat (noreply@blogger.com) at March 18, 2020 11:00 AM

Chromium Blog

New developer dashboard and registration flow for Chrome Web Store

Today we’re announcing two significant changes that affect the developer experience when publishing on the Chrome Web Store. The new developer dashboard is now the default experience, and the developer registration flow has changed.

New dashboard is now the default

We recently launched a new developer dashboard for Chrome Web Store developers to try out. Following a period of feedback and improvement, we’re announcing that this new dashboard is now the preferred dashboard. This dashboard appears by default on the following events:
  • When you click Settings > Developer Dashboard on the Chrome Web Store home page.
  • When you follow existing bookmarks or links to the developer dashboard.
  • When you navigate explicitly to chrome.google.com/webstore/developer/dashboard.
You can opt out of the default behavior by clicking Show more… in the small dialog at the bottom left-hand corner of the new dashboard, then clicking opt out:



Opting out means that you’ll see the old dashboard in each of the cases listed above. You can always opt in again by clicking the link in the old dashboard’s banner:


Opting out is useful for specific use cases that affect a small number of developers. The new dashboard does not yet support the following tasks:
  • Transfer items
  • Edit or publish a paid item, or add in-app purchases, using Chrome Web Store Payments
  • View an item’s public key
  • Re-order screenshots
  • Preview a new version of your item or promotional tiles
  • View revenue stats
For more details and status on these features see the known issues document.

Developer registration fee now required earlier

The Chrome Web Store charges a $5.00 fee to register as a Chrome Web Store developer. This fee was previously required only before publishing an item to the public, but is now required for all Chrome Web Store developers.

Who does this affect?

  • Developers who previously published items to the public were required to pay the registration fee at that time. These developers do not need to pay the fee again: no action is required.
  • New developers must register and pay this fee before they can use the Chrome Web Store developer dashboard.
  • Previously registered developers who have never published an item to the public must now pay this fee before they can use the CWS developer dashboard. If you have published to private domain or to trusted testers, but not to the public, you will now need to pay the registration fee. Note: This will look like a new developer registration flow, but all that’s required is to pay the fee and complete the flow.

Posted by Shumeng Gu, Chrome Web Store Engineer

by Chromium Blog (noreply@blogger.com) at March 18, 2020 04:26 AM

March 16, 2020

Google Chrome Releases

Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 81 (81.0.4044.66) 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

by Krishna Govind (noreply@blogger.com) at March 16, 2020 09:04 PM

Beta Channel Update for Desktop

The beta channel has been updated to 81.0.4044.69 for Windows, Mac, and, Linux.

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.



Prudhvikumar Bommana
Google Chrome

by Prudhvikumar Bommana (noreply@blogger.com) at March 16, 2020 10:42 AM

March 12, 2020

Google Chrome Releases

Dev Channel Update for Desktop

The Dev channel has been updated to 82.0.4083.0 for Windows, Mac, and Linux platforms.
A partial list of changes is available in the log. Interested in switching release channels? Find out how. 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.
Lakshmana Pamarthy Google Chrome

by Lakshmana Pamarthy (noreply@blogger.com) at March 12, 2020 11:30 AM

Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 81 (81.0.4044.62) 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.

Ben Mason
Google Chrome

by Ben Mason (noreply@blogger.com) at March 12, 2020 05:50 AM

March 11, 2020

Google Chrome Releases

Beta Channel Update for Desktop

The beta channel has been updated to 81.0.4044.62 for Windows, Mac, and, Linux.

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.



Prudhvikumar Bommana
Google Chrome

by Prudhvikumar Bommana (noreply@blogger.com) at March 11, 2020 10:30 AM

March 09, 2020

Igalia Chromium

Jacobo Aragunde: Mapping the input method implementations in Chromium

This is an overview of the different input method implementations in Chromium, centered in Linux platforms.

By Rime-devel – 小狼毫输入法界面 / Interface of Weasel Input Method, GPL, Link

Native IME

InputMethodAuraLinux is the central piece here. It implements two important interfaces and triggers the construction of the platform-specific bits. This is the structure for the Wayland/Ozone backend:

The InputMethodAuraLinux triggers the construction of a specific LinuxInputMethodContext through the Factory. In the case above, it would be an instance of WaylandInputMethodContext. It will save a reference to the Context while, at the same time, set itself as the delegate for that Context object. The set of methods of both classes is pretty similar, because they are expected to work together: the Context object, in the parts related to the platform, and InputMethodAuraLinux in the parts related to the rest of Chromium. It will interact with other system classes, mainly through the singleton object IMEBridge.

The X11 backend currently involves slightly different classes. It still has the InputMethodAuraLinux as a center piece, but uses different implementations for the Context and the ContextFactory: the multi-purpose class LinuxUI also acts as a factory. It’s expected to adapt to the Ozone structure at some point in the future.

ChromeOS and IME extension API

Chromium provides an extension API to allow the implementation of IMEs exclusively with web technologies. It shares code with the ChromeOS implementation.

The piece glueing the native infrastructure and the ChromeOS/Extension API implementations is the IMEEngineHandlerInterface, which has hooks to manage relevant events like focus in or out, process key events, etc. The singleton class IMEBridge can set an EngineHandler, which is an implementation of the aforementioned interface, and in the case that such implementation exists, it will receive those events from Chromium whenever they happen.

There is one base implementation of IMEEngineHandlerInterface called InputMethodEngineBase. It is extended by chromeos::InputMethodEngine, for the ChromeOS implementation, and by input_method::InputMethodEngine, for the IME extension API implementation.

The setup of the IME extension API contains the following pieces:

  • observers to the IME bridge
  • an InputIMEEventRouter that contains an instance of the InputMethodEngine class
  • a factory to associate instances of InputIMEEventRouter with browser profiles.
  • An InputImeAPI class that acts as several kinds of observers.
  • the actual code that backs every JavaScript IME operation, which makes use of the classes mentioned above and is contained in individual classes that implement UIThreadExtensionFunction for every operation.

The IME API operates in two directions: when one of the Javascript operations is directly called, it will trigger the native code associated to it, which would invoke any relevant Chromium code; when a relevant event happens in the system, the IMEBridgeObserver is notified and the associated JavaScript callback will be triggered.

by Jacobo Aragunde Pérez at March 09, 2020 05:00 PM

Google Chrome Releases

Stable Channel Update for Chrome OS

The Stable channel is being updated to 80.0.3987.137 (Platform version: 12739.94.0) for most Chrome OS devices. This build contains a number of bug fixes and security updates. Systems will be receiving updates over the next several days.

If you find new issues, please let us know by vising our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using 'Report an issue...' in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Daniel Gagnon
Google Chrome OS

by Daniel Gagnon (noreply@blogger.com) at March 09, 2020 02:11 PM

Stable Channel Update for Chrome OS

The Stable channel is being updated to 80.0.3987.128 (Platform version: 12739.87.0) for most Chrome OS devices. This build contains a number of bug fixes and security updates. Systems will be receiving updates over the next several days.

You can review new features here.

If you find new issues, please let us know by vising our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using 'Report an issue...' in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Daniel Gagnon
Google Chrome OS

by Daniel Gagnon (noreply@blogger.com) at March 09, 2020 02:06 PM

March 06, 2020

Google Chrome Releases

Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 81 (81.0.4044.42) 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.

Ben Mason
Google Chrome

by Ben Mason (noreply@blogger.com) at March 06, 2020 11:29 AM