![Rachel Andrew](https://web.dev/images/authors/rachelandrew.jpg) Rachel Andrew Technical Writer [GitHub](https://github.com/rachelandrew) [LinkedIn](https://www.linkedin.com/in/rachelandrew) [Mastodon](https://front-end.social/@rachelandrew) [Bluesky](https://bsky.app/profile/rachelandrew.bsky.social) [Homepage](https://rachelandrew.co.uk)

<br />


Published: January 13, 2026

<br />

Chrome 144 is rolling out now, and this post shares some of the key features
from the release. Read the full [Chrome 144 release notes](https://developer.chrome.com/release-notes/144.md.txt).

Highlights from this release:

- [Highlight find-in-page search text](https://developer.chrome.com/blog/new-in-chrome-144.md.txt#search-text) with a new pseudo-element.
- Request permission to use location date with [the `<geolocation>`
  element](https://developer.chrome.com/blog/new-in-chrome-144#geolocation).
- [The Temporal API](https://developer.chrome.com/blog/new-in-chrome-144.md.txt#temporal) brings a modern date and time API to the web.

## The `::search-text` pseudo-element

Exposes find-in-page search result styling as the `::search-text` pseudo-element,
which is a highlight pseudo-element like those used for selection and spelling
errors. This lets you change the foreground and background colors or add text
decorations. This is especially useful if the browser defaults have insufficient
contrast with the page colors or are otherwise unsuitable.

Learn more on the Igalia blog in
[Find-in-Page Highlight Styling](https://blogs.igalia.com/schenney/find-in-page-highlight-styling/).

## The `<geolocation>` element

Introduces the `<geolocation>` element, a declarative, user-activated control
for accessing the user's location. It streamlines the user and developer journey
by handling the permission flow and directly providing location data to the
site, often eliminating the need for a separate JavaScript API call.

This addresses the long-standing problem of permission prompts triggered
directly from JavaScript without a strong signal of user intent. By embedding a
browser-controlled element in the page, the user's click provides a clear,
intentional signal. This provides a better prompt user experience and,
crucially, a recovery path for users who have previously denied the permission.

Learn more in [Introducing the HTML `<geolocation>` element](https://developer.chrome.com/blog/geolocation-html-element.md.txt).

## The Temporal API

The Temporal API in ECMA262 provides standard objects and functions for working
with dates and times. Date has been a long-standing issue in ECMAScript.
`Temporal`, a global `Object` that acts as a top-level namespace (for example,
`Math`), bringing a modern date and time API to the ECMAScript language.

For a detailed breakdown of motivations, see
[Fixing JavaScript Date: Getting Started](https://maggiepint.com/2017/04/09/fixing-javascript-date-getting-started/), and check out the
[MDN documentation for Temporal](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Temporal).

## Further reading

This covers only some key highlights. Check the following links for additional
changes in Chrome 144.

- [Release notes for Chrome 144](https://developer.chrome.com/release-notes/144.md.txt).
- [What's new in Chrome DevTools (144)](https://developer.chrome.com/blog/new-in-devtools-144.md.txt).
- [ChromeStatus.com updates for Chrome
  144](https://chromestatus.com/features#milestone%3D144).
- [Chrome release calendar](https://chromiumdash.appspot.com/schedule).

## Subscribe

To stay up to date, [subscribe](https://goo.gl/6FP1a5) to the [Chrome Developers
YouTube channel](https://www.youtube.com/user/ChromeDevelopers/), and you'll get
an email notification whenever we launch a new video. Or follow us on X or
LinkedIn for new articles and blog posts.

As soon as Chrome 145 is released, we'll be right here to tell you what's new in
Chrome!