Chrome 109

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

Enabled by default in 109

This release of Chrome had 10 new features.

Auto range support for font descriptors inside @font-face rule

Auto range support for variable fonts in 'font-weight', 'font-style' and 'font-stretch' descriptors inside '@font-face' rule. #

This feature was specified in this Spec.

CSS 'lh' Length Unit

The 'lh' unit adds support for expressing CSS lengths relative to the line-height. That is typically useful for specifying the height of an element to fit a whole number of lines. Example: textarea { height: 5lh } #

This feature was specified in this Spec.

CSS `hyphenate-limit-chars` property

Specifies the minimum number of characters in a hyphenated word. When applying the hyphenation, the optimal minimum number of characters in the word, before the hyphen, or after the hyphen can vary by the design of the page, or by the language. This property allows the finer grained control of the hyphenation. #

This feature was specified in this Spec.

HTTP response status code in Resource Timing

Adds a field to PerfomanceResourceTiming to indicate the HTTP response status when the resource was fetched. #

This feature was specified in this Spec.

Resources

Docs: https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md

No linked samples

MathML

Supports MathML Core, a language for describing mathematical notation embeddable in HTML and SVG. MathML is rendered in a CSS-compatible way with OpenType MATH and exposed via platform accessibility APIs. MathML styling is enabled by CSS features including those dedicated to math layout (math-depth, math-shift and math-style properties, 'math' display value, 'math' font-family name and 'math-auto' text-transform). Finally, the MathMLElement interface provides a convenient way to manipulate MathML in scripts. #

This feature was specified in this Spec.

Resources

Docs: https://drafts.csswg.org/css-fonts-4/#valdef-font-family-mathhttps://w3c.github.io/mathml-aamhttps://docs.google.com/document/d/1biGEaWN8ThNTDtAbT1M5GIf6N5uQLWdxh2QhrG9uN5chttps://docs.google.com/document/d/1bvY_Npe2zLW_705KXdmecsH6P9I9wBMpHRsZ9CxWNOI/edit#heading=h.u9hwm9tp8nuyhttps://developer.mozilla.org/en-US/docs/Web/MathMLhttps://developer.mozilla.org/en-US/docs/Learn/MathML

Samples: https://people.igalia.com/fwang/2022-06-igalia-week-shipping-mathml-in-chromium/#/12https://fred-wang.github.io/MathFonts

MediaTrackSupportedConstraints.suppressLocalAudioPlayback

Consider a Web application APP which is display-capturing a tab TAB. We add a mechanism by which APP may control whether the audio playing in TAB would be played out of the user’s local speakers. #

This feature was specified in this Spec.

Origin Private File System (OPFS) on Android

Enable the Origin Private File System (OPFS) part of File System Access API on Android. This includes all of the File System Access API surface, minus show*Picker() methods and Drag-and-Drop API integration. With FSA API on OPFS, a site can access its per-origin, private file system and are able to perform file operations via `FileSystemSyncAccessHandle` with improved performance. The original API, including both OPFS and non-OPFS, was shipped in M86 for desktop, and the extension with SyncAccessHandle was shipped in M102. https://chromestatus.com/feature/6284708426022912 https://chromestatus.com/feature/5702777582911488 #

This feature was specified in this Spec.

Resources

Docs: https://web.dev/file-system-access/#accessing-the-origin-private-file-system

No linked samples

Same-site cross-origin prerendering triggered by the speculation rules API

Previously [1] we launched same-origin prerendering triggered by the speculation rules API. This expands coverage to also allow triggering same-site cross-origin pages [2]. This prerendering will be done with credentials and storage access, but such prerender targets will need to opt in by using the `Supports-Loading-Mode: credentialed-prerender` header. [1]: https://chromestatus.com/feature/5355965538893824 [2]: https://web.dev/same-site-same-origin/ #

This feature was specified in this Spec.

Resources

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

No linked samples

Snap border, outline and column-rule widths before layout

Snap border, outline and column-rule widths before layout to avoid gaps between backgrounds and borders caused by paint-time snapping. With this change, Blink will match Gecko and WebKit. #

This feature was specified in this Spec.

WebTransport BYOB readers

Support BYOB(bring-your-own-buffer) readers for WebTransport to allow reading into a developer-supplied buffer. BYOB readers can minimize buffer copies, as well as reduce memory allocations. #

This feature was specified in this Spec.

Resources

No linked docs

Samples: https://webrtc.internaut.com/wc/wtSender4

Origin Trials in-progress in 109

This release of Chrome had 1 new origin trials.

Conditional Focus

Extend the getDisplayMedia() API by adding a CaptureController object which can be passed in as a parameter. This object exposes a setFocusBehavior() method. By calling this method, an app can control whether the captured tab/window is focused when capture starts, or whether the capturing page should retain focus. #

This feature was specified in this Spec.

Resources

Docs: https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM

Samples: https://wicg.github.io/conditional-focus/demo

Flagged features in 109

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:

• They are superseded by newer APIs.
• They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
• They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.

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:

• Announce on the blink-dev mailing list.
• Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
• Wait, monitor, and then remove the feature as usage drops.

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 109

This release of Chrome had 0 features deprecated.

Removed features in 109

This release of Chrome had 1 features removed.

Deprecate Event.path

Event.path is a non-standard API that returns the event's path, which is an array of the objects on which listeners will be invoked. It is supported by Blink only, causing web compatibility issues. Web developers should switch to the equivalent standard API Event.composedPath(), which returns the same result. #

This feature was specified in this Spec.