'Google Chrome 143' stable release, ICU version upgraded to 77

The latest stable version of the Google Chrome web browser, version 143, has been released. The Unicode support library ICU has been upgraded to version 77, which supports Unicode version 16.0.0, and locale data has also been updated. Japanese is one of the locales affected, so web content that relies on specific formats should be aware of the impact of this update.

Chrome 143 | Release notes | Chrome for Developers
https://developer.chrome.com/release-notes/143

◆ICU 77: Supports Unicode version 16.0.0
The Unicode support library, ICU (International Components for Unicode) , will be upgraded from version 74.2 to 77.1. The ICU update supports Unicode version 16.0.0 and also updates locale data. This will have the following impact:

- In the Italian locale, the thousands separator for four-digit numbers is omitted (1.234 → 1234).
- In some English locales, a comma is added after the day of the week ('Saturday 30 April 2011' becomes 'Saturday, 30 April 2011')
- Many small changes to Intl and RegExp (V8)
・IDNA upgrade
Text segmentation: Improved line breaks in Japanese when using ' word-break : auto-phrase'

The 'Text Segmentation' change is related to the ' Changes to Japanese Line Breaking Rules ' implemented in Chrome 119. While neither of these changes will usually cause problems, if your web content is expected to be displayed in a specific format, the update may affect it and cause unexpected behavior, so developers of the relevant content should be aware of this.

◆CSS: Anchors, Fallbacks, and Container Queries
CSS introduces ' @container anchored(fallback)', which styles the descendants of an anchored element based on the applied position-try-fallbacks value.
[code]
#anchored {
position-try-fallbacks: flip-block;
container-type: anchored;
}

@container anchored(fallback: flip-block) {
#anchored > .arrow {
--arrow-rotation: 180deg;
}
}
[/code]

This query allows you to style the tether and animation of an anchor element based on its relative position to the anchor.

◆ EditContext API: TextFormat underlineStyle and underlineThickness
The EditContext API released by Chromium contained a bug that has now been fixed. Specifically, the TextFormat object provided by the textformatupdate event was returning an incorrect combination of values for the underlineStyle and underlineThickness properties. This has now been corrected.

・{“ None ”, “ Solid ”, “ Dotted ”, “ Dashed ”, “ Squiggle ”} → {“ none ”, “ solid ”, “ dotted ”, “ dashed ”, “ wavy ”}
・{“ None ”, “ Thin ”, “ Thick ”} → {“ none ”, “ thin ”, “ thick ”}

◆CSS: font-language-override
CSS now implements the font-language-override property, which allows you to override the system language used for OpenType glyph substitution by specifying a language tag.
[code]
font-language-override: 'ENG'; /* English glyphs */
font-language-override: 'TRK'; /* Turkish glyphs */
[/code]

This allows for fine-grained typography control, making it convenient for multilingual content and for using fonts with language-specific glyph variants.Until now, Chromium's OpenType glyph substitution was completely dependent on the system's language settings, but this update brings it into line with Firefox.

◆DataTransfer property of input event to contenteditable element
To allow access to clipboard and drag-and-drop data during edit operations on contenteditable elements, the dataTransfer property of InputEvent is set to inputType as insertFromPaste, insertFromDrop, or insertReplacementText. The dataTransfer object contains the same data as was used in the beforeinput event. Note that this change only applies to contenteditable elements and does not apply to general form controls such as <textarea> or <input>.

◆IWA: Web Smart Card API
Web Smart Card API is now supported for Independent Web Apps (IWA) . This feature allows you to migrate your smart card applications to the web platform. Administrators can control the availability of this API in two ways:

Global : Use the DefaultSmartCardConnectSetting policy
Per app : Use the SmartCardConnectAllowedForUrls and SmartCardConnectBlockedForUrls policies

◆Gamepad: Support for ongamepadconnected and ongamepaddisconnected event handler attributes
Add the ongamepadconnected and ongamepaddisconnected event handlers to the WindowEventHandlers interface mixin, which enables the following event handler attributes:

・window.ongamepadconnected
・document.body.ongamepadconnected
・window.ongamepaddisconnected
・document.body.ongamepaddisconnected

◆ Specify background-position-x/y all at once
The background-position shorthand property allows you to specify a position relative to one of the edges of a background image.
[code]
.element {
background-image: url(flower.gif);
background-repeat: no-repeat;
background-position-x: left 30px;
background-position-y: bottom 20px;
}[/code]

◆Other updates
JavaScript: DOM API now accepts more characters
FedCM : Supports structured JSON responses from IdPs
Speculation rules : Improved eagerness on mobile
- Web App Manifest : Added an algorithm for updating targets to the manifest specification.
WebGPU : Texture component swizzling allows GPUTextureViews to rearrange and replace color components.
WebTransport Application Protocol Negotiation: Allows you to negotiate the protocol used within the WebTransport handshake.

◆Origin Trial
・Digital Credentials API : Supports issuing digital credentials
TCP socket: Randomize connection pool limit

◆Scheduled for abolition/phased out
- Deprecated the getter for Intl Locale Info
XSLT is deprecated
FedCM Privacy Enforcement for Client Metadata: Prohibits misuse of metadata to associate user IDs across multiple sites
FedCM: Moved the nonce parameter from the top level to a field in the params object
FedCM: Renamed the code attribute of IdentityCredentialError to error

Google Chrome 143 also includes 13 security bug fixes .

The next stable version, 'Google Chrome 144,' is scheduled to be released on Tuesday, January 13, 2026 local time.