Along with the Chrome 99 stable release a few days ago, Edge 99 stable, also based on Chromium, was released today. For those using multiple accounts in the Edge browser, the new version allows users to create a custom list of websites for each account. When you launch a website mentioned in the custom list, Edge will automatically open it in your preferred account.
The new version also optimizes the browsing experience of PDF documents, and users can simply use the page thumbnails in the left pane to jump between pages. There are also some improvements in password management. You can use the PasswordManagerBlocklist policy to determine a list of domains for which you do not want to use a password manager. Autofill workflows for these fields will be disabled.
As it is about to enter the three-digit number, Edge 99 has also begun to make some preparations, and will send a three-digit version number in the User-Agent header, such as “Edge/100”. Starting in Microsoft Edge 97, site owners can test this upcoming proxy string by enabling the #force-major-version-to-100 experimental flag in edge://flags to ensure their user agent parsing logic is Robust and works as expected.
Another interesting feature is the option to set a custom master password. Edge users can now define a custom string as their master password. Only if they first authenticate with this string will they be able to take advantage of the autofill feature to get the credentials on the web page. The purpose of this is to prevent unauthorized users from using your saved passwords by adding another layer of security.
In the upcoming Chromium 100 release, mainly new APIs have been added, including the Multi-Screen Window Placement API and the Digital Goods API. The Multi-Screen Window Placement API is designed to better handle multi-window applications and other similar use cases that require the precise positioning of certain windows. Among the use cases for the multi-screen window placement API are slideshows across screens, financial applications for windowed dashboards across monitors, medical imaging applications, creative applications across multiple screens, and more.
The Digital Goods API is used to query/manage digital products for in-app purchases from web apps. Web apps within the Google Play Store can now easily accept purchases of digital goods. The Digital Goods API was initially seen as a provenance experiment.