![\"Chrome](\"\/wp-content\/uploads\/2021\/10\/811cf6946180b1f5d59c7546ab670ed4.jpg\")
<\/center>\nIt is noted that exception handling at the WebAssembly level significantly reduces the size of the generated code compared to JavaScript exception handling. For example, using the Binaryen optimizer with JavaScript exception handling leads to a 43% increase in code size, while WebAssembly handling results in only a 9% increase. Additionally, when using the optimization mode «-O3», the code with WebAssembly exception handling performs almost identically to the code without exception handlers, whereas JavaScript exception handling slows execution by 30%. <\/p>\n
- \n
- Trimming information in the HTTP header User-Agent and JavaScript parameters navigator.userAgent, navigator.appVersion, and navigator.platform is included. The header retains only details about the browser name, major version, platform, and device type (mobile, PC, tablet). For additional data such as the exact version and extended platform details, the User Agent Client Hints API must be used. The start of User-Agent trimming for regular user systems is planned for the release of Chrome 102, which will be published in six months.\n
- The possibility of creating Access Handles for the File System Access API is proposed, allowing web applications to read and write data directly to files and directories on the user's device. To streamline access methods for web applications to the file system, Google plans to combine the File System Access API and Storage Foundation. As a preparatory step for such a merger, support for access handles is proposed, which complements file descriptor-based methods with enhanced capabilities, such as setting write locks by other processes and creating separate streams for writing and reading, including support for reading and writing from workers in synchronous mode. <\/ul>\n
- The Secure Payment Confirmation API has been stabilized and is enabled by default, with the implementation of a new 'payment' extension that provides an additional confirmation for payment transactions. The verifying party, such as a bank, can generate a PublicKeyCredential, which the merchant can request for additional secure payment confirmation through the Payment Request API using the 'secure-payment-confirmation' payment method.\n
- In callback invocations set up through the PerformanceObserver constructor, the droppedEntriesCount property has been implemented, allowing insight into how many site performance metrics were discarded due to not fitting into the provided buffer.\n
- The EyeDropper API has been added, allowing the invocation of a browser-provided interface to determine the color of arbitrary pixels on the screen, which can be used in graphic editors implemented as web applications. const eyeDropper = new EyeDropper(); const result = await eyeDropper.open(); \/\/ result = {sRGBHex: ‘#160731’}\n
- The self.reportError() function has been added, allowing scripts to log errors to the console, emulating the occurrence of an unhandled exception.\n
- The URLPattern API has been added to check if a URL matches a specific pattern, which can be used for parsing links and redirecting requests to handlers in a service worker. const p = new URLPattern({ protocol: ‘https’, hostname: ‘example.com’, pathname: ‘\/:folder\/*\/:fileName.jpg’, });\n
- The Intl.DisplayNames API has been expanded, allowing for the retrieval of localized names for languages, countries, currencies, date elements, and more. The new version includes new name types 'calendar' and 'dateTimeField', which provide localized names for calendars and date\/time fields (for example, month names). Support for dialect usage has been added for the 'language' type.\n
- The Intl.DateTimeFormat API has added support for new values of the timeZoneName parameter: 'shortGeneric' for displaying a short time zone identifier (e.g., 'PT', 'ET'), 'longGeneric' for long (e.g., 'Pacific Time', 'Mountain Time'), 'shortOffset' for a short offset from GMT (e.g., 'GMT+5'), and 'longOffset' for a long offset from GMT (e.g., 'GMT+0500').\n
- The U2F API (Cryptotoken) has been deprecated, and it should be replaced with the Web Authentication API. The U2F API will be disabled by default in Chrome 98 and completely removed in Chrome 104.\n
- Improvements have been made to the web developer tools. The Styles panel has simplified the adjustment of CSS properties related to dimensions (height, padding, etc.). The Issues tab now allows individual issues to be hidden. The web console and the Sources and Properties panels have enhanced the display of properties (custom properties are now bolded and shown at the top of the list).
![\"Chrome](\"\/wp-content\/uploads\/2021\/10\/29b935c04a5a8790cfc8c118d221fa40.jpg\")
<\/center> <\/ul>\n