Published: April 29, 2025
Chrome 136 is rolling out now, and this post shares some of the key features from the release. Read the full Chrome 136 release notes.
Highlights from this release
- Use the static RegExp.escape method for strings used inside a regular expression.
:visited
link history is now partitioned- You can now upgrade existing password credentials to a passkey.
- And plenty more.
RegExp.escape
is now Baseline Newly available
The
RegExp.escape
static method has landed across all browsers within a few
months, and becomes Baseline Newly available as it lands in Chrome 136.
This method escapes any potential regular expression syntax characters in a string,
returning a new string that can be safely used as a literal pattern for the
RegExp()
constructor.
:visited
link history is now partitioned
To eliminate user browsing history leaks, anchor elements are styled as :visited
only if they have been clicked from this top-level site and frame origin before.
By only styling links that have been clicked on this site and frame before, the many side-channel attacks that have been developed to obtain :visited
links styling information are now obsolete. They no longer provide sites with new information about users.
Learn more about these
improvements to the privacy of :visited
links.
Upgrade credentials to passkeys
WebAuthn Conditional Create requests let a website (known as a Relying Party or RP) create a passkey without prominent modal mediation, if the user has previously consented to credential creation.
The main use case is commonly referred to as "passkey upgrades". That is, if the browser or credential manager already stores an existing password credential for the same relying party and user, conditional create lets the website automatically create a matching passkey.
And more!
Of course there's plenty more.
- The
dynamic-range-limit
property enables a page to limit the maximum brightness of HDR content. - You can now add a tag field to speculation rules. This optional field can be used to track the source of speculation rules.
- FecCM can now show multiple identity providers in the same dialog, by having all providers in the same
get()
call.
Further reading
This covers only some key highlights. Check the following links for additional changes in Chrome 136.
- Release notes for Chrome 136.
- What's new in Chrome DevTools (136).
- ChromeStatus.com updates for Chrome 136.
- Chrome release calendar.
Subscribe
To stay up to date, subscribe to the Chrome Developers YouTube channel, 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 137 is released, we'll be right here to tell you what's new in Chrome!