'Google Chrome 136' stable release, existing authentication information can be upgraded to a passkey
The latest stable version of the web browser Google Chrome , version 136, has been released. You can now upgrade your saved password credentials to
New in Chrome 136 | Blog | Chrome for Developers
https://developer.chrome.com/blog/new-in-chrome-136
◆Upgrade your credentials to a passkey
WebAuthn 's conditional creation request allows a passkey to be created without a noticeable screen if the user previously consented to creating credentials. The primary use case for this feature is 'upgrade to passkey': if you already have credentials stored for a website in your browser or password manager, the conditional creation request allows the website to automatically create a matching passkey.
◆:Improved privacy protection for visited links
To prevent leaking a user's browsing history, anchor elements will now only have the :visited style applied if they have been previously clicked on in the top-level site and frame origin.
To explain this in a bit more detail, imagine you click on a link on a website.
Previously, the link you clicked would appear in your browsing history, and all sites that contained the same link would show the link as :vidited. If that link was also on a malicious site, the site would know that you had 'visited' the link.
Now your browsing history will be partitioned so only links you have clicked on a site will be :vidited, meaning malicious sites will not be able to see your link browsing history.
◆RegExp.escape()
RegExp objects that support regular expressions implement a static method escape() that takes a string as an argument and returns a string that is safe to use as a literal pattern by properly escaping any characters that might be interpreted as regular expression syntax characters.
RegExp.escape() is primarily intended for use in RegExp object constructors when the string passed to them may contain regular expression syntax characters. In such cases, you can prevent unexpected behavior by processing the string with RegExp.escape() beforehand.
◆Other updates
dynamic-range-limit : A CSS property is now available to limit the maximum luminance of HDR content.
- Improved inference rules : You can now add tag fields.
FedCM Improvements: It is now possible to include all providers in the same get() and show multiple identity providers in the same dialog.
Additionally, Google Chrome 136 includes eight security bug fixes .
The next stable version, Google Chrome 137, is scheduled to be released on Tuesday, May 27, 2025 local time.
Related Posts:
in Software, Posted by log1c_sh