Chrome Release Summary

Chrome version: 132, 131, 130, 129, 128, 127, 126, 125, 124, 123, 122, 121, 120, 119, 118, 117, 116, 115, 114, 113, 112, 111, 110, 109, 108, 107, 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0

Chrome 103

Enabled (12) | Origin Trial (0) | Behind a flag (0) | Deprecated (0) | Removed (1)

Enabled by default in 103

This release of Chrome had 12 new features.

"deflate-raw" compression format

Add a new compression format, "deflate-raw", to give web developers access to the raw deflate stream without any headers or footers. This is needed, for example, to read and write zip files. #

This feature was specified in this Spec.

103 Early Hints for Navigation

Support 103 Early Hints informational responses during top-level frame navigation. When a 103 response includes link headers Chromium tries to preload specified resources (including modulepreload) or preconnect to specified origins before the final response is received. This gives Web developers a way to optimize Core Web Vitals such as Largest Contentful Paint (LCP). #

This feature was specified in this Spec.

Resources

Docs: https://docs.google.com/document/d/1gCh_CnfrJq_VL7aGoq6skc7sn4yn5pKsM0gkHe5B9go/edit?usp=sharing

Samples: https://early-hints.fastlylabs.com/

ARIA Attribute Reflection for role attribute

This feature provides a JavaScript API to allow web developers to query and modify the "role" ARIA attribute directly. This implements attribute reflection for "role" attribute, similar to other attributes already supported like "ariaDescription" or "ariaRequired". #

This feature was specified in this Spec.

AbortSignal.timeout() Static Method

Returns a new AbortSignal object that is automatically aborted after a given number of milliseconds. This method can be used by developers to easily implement timeouts for signal-accepting async APIs, e.g. fetch(). #

This feature was specified in this Spec.

Resources

No linked docs

Samples: https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal/timeout

Add .avif to permitted Web Share file extensions

The .avif image file should be able to be shared by Web Share. Adding avif to the other allowed image file types will help spread the use of it. #

This feature was specified in this Spec.

Allow popstate to fire before load

Before this change, Chromium would fire hashchange asynchronously (after a task), and delay popstate until the load event. This means the event ordering could be either [hashchange, popstate], or [popstate, hashchange], depending on how long the document took to load. After this change, Chromium will match Firefox and always fire popstate immediately upon URL changes, i.e. the order will always be [popstate, hashchange]. #

This feature was specified in this Spec.

Block external protocol in sandboxed iframe

Block sandboxed iframe from opening external application. To enable it again, apply at least one of following values to the <iframe> element's sandbox property: - allow-popups - allow-top-navigation - allow-top-navigation-with-user-activation Or use the new dedicated one: - allow-top-navigation-to-custom-protocols #

This feature was specified in this Spec.

Resources

Docs: https://docs.google.com/document/d/1hHjxQk1yLoC0ioBBYpIq4JJYAwj9sJfR5b62QcLt1eM/edithttps://github.com/whatwg/html/pull/7124https://github.com/whatwg/html/pull/7654

No linked samples

Local Font Access

Gives web applications the ability to enumerate local fonts and some metadata about each. Also gives web applications access to table data stored within local fonts, allowing those fonts to be rendered within their applications using custom text stacks. #

This feature was specified in this Spec.

Resources

Docs: https://web.dev/local-fontshttps://bit.ly/2HWBOLihttps://developer.chrome.com/blog/insider-april-2022/#local-fonts-access-api

Samples: https://font-access-api.glitch.me

Restrict Gamepad usage

Requires a secure context for the Gamepad API and adds a feature policy to allow restricting gamepad use. #

This feature was specified in this Spec.

Resources

Docs: https://docs.google.com/document/d/1Dj_7EpT9ttnI96BuNXtLEJkHEq0orHgoLeYaOBz9xsU/edit?usp=sharing

No linked samples

SerialPort forget()

Following the recent HIDDevice[1] and USBDevice[2] forget() additions to the web platform, the SerialPort forget() method allows web developers to voluntarily revoke a permission to a SerialPort that was granted by a user. [1] https://groups.google.com/a/chromium.org/g/blink-dev/c/Fk-IJF63UWc [2] https://groups.google.com/a/chromium.org/g/blink-dev/c/pSM2W0TtKEI/ #

This feature was specified in this Spec.

Resources

Docs: https://web.dev/serial/#revoke-access

No linked samples

Update User-Agent Client Hints GREASE implementation

We seek to align our implementation of GREASE in User Agent Client Hints with the current spec, which includes additional GREASE characters beyond the current semicolon and space, and which recommends varying the arbitrary version. This is to help prevent bad assumptions from being built on top of User-Agent strings. #

This feature was specified in this Spec.

User Activation Requirement for SPC Credential Enrollment

This intent is to add a user activation requirement for Secure Payment Confirmation (SPC) credential enrollment in a cross-origin iframe to help mitigate a privacy issue (see https://github.com/w3c/secure-payme for discussion of a potential identity tracking attack). #

This feature was specified in this Spec.

Origin Trials in-progress in 103

This release of Chrome had 0 new origin trials.

Flagged features in 103

This release of Chrome had 0 are available behind a flag.

Deprecations and Removals

Deprecation policy

To keep the platform healthy, we sometimes remove APIs from the Web Platform which have run their course. There can be many reasons why we would remove an API, such as:

Some of these changes will have an effect on a very small number of sites. To mitigate issues ahead of time, we try to give developers advanced notice so they can make the required changes to keep their sites running.

Chrome currently has a process for deprecations and removals of API's, essentially:

You can find a list of all deprecated features on chromestatus.com using the deprecated filter and removed features by applying the removed filter. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.

Deprecated features in 103

This release of Chrome had 0 features deprecated.

Removed features in 103

This release of Chrome had 1 features removed.

Remove Battery Status API on Insecure Origins

Deprecate and remove the Battery Status API on insecure origins, such as HTTP pages or HTTPS iframes embedded in HTTP pages. #

This feature was specified in this Spec.