Press "Enter" to skip to content

Chrome 157 Brings On‑Device Language Detection and Major CSS Updates

Google has rolled out Chrome 157 as the newest stable version of its widely used web browser. The update arrives with a notable on‑device language detection capability for Android, a collection of CSS extensions, and a range of security‑focused adjustments. In total, the release patches 213 security vulnerabilities and sets the stage for the next stable build, Chrome 158, expected on 17 November 2026.

On‑device language detection for Android

Android users of Chrome can now access a Language Detector API that evaluates the language of a given text snippet. Developers feed text to the API via JavaScript, and the built‑in machine‑learning model returns the identified language. Because the inference runs locally, no data leaves the device, which enhances privacy and reduces network traffic. When the model is already present on a device, the detection works even without an internet connection, opening possibilities for offline applications.

Potential use cases include automatically recognizing the language a user has typed and prompting translation services or other multilingual features. By keeping the processing on the device, the design also aligns with business scenarios that handle highly confidential text, where sending data to external servers would be undesirable.

Expanded CSS capabilities

The release adds a new corner property that consolidates corner‑shaping directives into a single declaration. Previously, developers needed to combine border-radius with a separate corner-shape rule; the new property streamlines that workflow. Additional derived properties target individual corners, such as corner-top, corner-bottom-left, and directional variants like corner-block-start, which respect the text’s writing direction.

Text handling receives more flexibility as well. The text-overflow property now accepts arbitrary strings, allowing developers to replace the default ellipsis with custom markers like “(continued)” when content exceeds its container. A new text-decoration-inset attribute lets designers adjust the length of underlines, overlines, and strikethroughs, making it possible to shorten or extend these decorations beyond the text edges.

Positioning rules have also been refined. The position-visibility property now recognizes anchor-valid and anchor-visible, while retaining the older plural forms anchors-valid and anchors-visible as compatibility aliases. When anchor-valid is employed, the specification targets only the default anchor for evaluation, simplifying anchor‑based layout calculations.

Security, API, and other technical updates

On the security front, Chrome 157 introduces a javascriptURLs option within the HTML Sanitizer API, granting developers finer control over the sanitization of JavaScript URLs. The Background Fetch API is now bound by Cross‑Origin Resource Sharing (CORS) rules, mirroring the restrictions applied to the standard Fetch API and helping to prevent circumvention of network policies.

Service Workers gain access to a ProgressEvent object, enabling them to emit progress updates with properties such as lengthComputable, loaded, and total. The Web Bluetooth API sees its BluetoothRemoteGATTServer class inherit from EventTarget, which makes event‑listener methods like addEventListener() usable on Bluetooth server objects.

Additional enhancements include support for rendering HTML inside a canvas element via an HTML‑in‑canvas feature, the introduction of the atomic-vec2u-min-max type in WebGPU, and new timing controls—styleDuration and forcedStyleDuration—in the Long Animation Frames API. A capability for displaying icon‑only buttons within Capability Elements remains under review.

The release notes also list two origin trials: “Connection Allowlists – Embedded Enforcement” and “Overscroll Areas.” Both trials allow developers to experiment with emerging features before they become standard.

Overall, the on‑device language detection stands out as the headline feature, offering a privacy‑preserving alternative to cloud‑based language models. For web application developers, the addition expands the toolbox for building translation and multilingual experiences without compromising user data.

The CSS extensions aim to reduce the amount of repetitive code front‑end engineers must write, while also granting designers greater expressive power when shaping UI elements. However, because support for many of the new properties may differ across browsers, developers are likely to adopt a phased rollout strategy that includes fallback mechanisms.

With 213 security bugs addressed, Chrome 157 reinforces the browser’s safety posture while delivering a broad set of functional upgrades. The upcoming Chrome 158, slated for release in mid‑November 2026, promises to continue this trajectory of performance, privacy, and developer‑centric enhancements.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *