![\"Release](\"\/wp-content\/uploads\/2021\/09\/57118b24bf034d008bdc7437e0a952c1.png\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2021\/09\/a911bdb4398ed776a67765e2f8e23a4c.png\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2021\/09\/59e3250430d6bee471bbe0c2ba6ebfb8.png\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2021\/09\/2c4a26e76713da7c8dd40a0396c6b788.png\")
<\/center>\n- \n
- The WebGPU API has been introduced to replace the WebGL API, providing tools for performing operations on the GPU, such as rendering and computations. Conceptually, WebGPU is similar to the Vulkan, Metal, and Direct3D 12 APIs. WebGPU differs from WebGL in much the same way as the Vulkan graphics API differs from OpenGL; however, it does not rely on any specific graphics API, serving instead as a universal layer that utilizes the same low-level primitives found in Vulkan, Metal, and Direct3D 12.\n
WebGPU provides JavaScript applications with low-level control over the organization, processing, and dispatching of commands to the GPU, as well as managing associated resources, memory, buffers, texture objects, and compiled graphics shaders. This approach enables higher performance for graphics applications by reducing overhead and increasing efficiency in GPU operations. The API also allows for the creation of complex 3D projects for the web that perform comparably to standalone applications while remaining platform-agnostic. <\/p>\n
- Standalone PWA applications now have the capability to register as URL handlers. For example, the application music.example.com can register itself as the handler for the URL https:\/\/*.music.example.com, and all transitions from external applications using these links, such as from messengers and email clients, will lead to opening this PWA application instead of a new tab in the browser.\n
- Support for the new HTTP response code \u2014 103 has been implemented, which can be used for proactive header delivery. Code 103 allows informing the client about the content of certain HTTP headers immediately after the request, without waiting for the server to complete all operations related to the request and begin delivering content. Similarly, hints about related elements on the delivered page that can be preloaded (e.g., links to CSS and JavaScript used on the page) can be provided. Upon receiving information about such resources, the browser will start loading them without waiting for the main page to finish delivering, reducing the overall request processing time. <\/ul>\n
- The WebCodecs API has been added to manipulate multimedia streams at a low level, complementing high-level APIs like HTMLMediaElement, Media Source Extensions, WebAudio, MediaRecorder, and WebRTC. The new API may be in demand in areas such as game streaming, client-side effects application, stream transcoding, and support for non-standard multimedia containers. Instead of implementing individual codecs in JavaScript or WebAssembly, the WebCodecs API provides access to high-performance components built into the browser. Specifically, the WebCodecs API includes decoders and encoders for audio and video, image decoders, and functions for working with individual video frames at a low level.\n
- The Insertable Streams API has been stabilized, allowing manipulation of raw multimedia streams transmitted through the MediaStreamTrack API, such as data from cameras and microphones, screen capture results, or intermediate decoding data from codecs. Interfaces from WebCodec are used to represent raw frames, after which a stream is formed, similar to what the WebRTC Insertable Streams API generates based on RTCPeerConnections. Practically, the new API enables functionalities such as applying machine learning methods for object identification or annotation in real-time, or adding effects like background removal before encoding or after decoding by a codec.\n
- The method scheduler.postTask() has been stabilized, allowing management of task scheduling (JavaScript callback calls) with varying priority levels. Three priority levels are provided: 1 - executed first, even if user operations may be blocked; 2 - visible changes are allowed; 3 - execution in the background. The TaskController object can be used to change priorities and cancel tasks.\n
- The API Idle Detection is now stabilized and expands beyond Origin Trials to determine user inactivity. The API can detect when the user is not interacting with the keyboard\/mouse, the screensaver is active, the screen is locked, or work is being done on another monitor. The application is notified of inactivity through a notification sent after the specified inactivity threshold is reached.\n
- The process of color management in CanvasRenderingContext2D and ImageData objects has been formalized, incorporating the sRGB color space. It is now possible to create CanvasRenderingContext2D and ImageData objects in color spaces other than sRGB, such as Display P3, to utilize the enhanced capabilities of modern monitors.\n
- The VirtualKeyboard API has been enhanced with methods and properties to control the display and hiding of the virtual keyboard, as well as to retrieve information about the size of the displayed virtual keyboard.\n
- JavaScript classes now support static initialization blocks to group code that runs once when the class is processed: class C { \/\/ The block will run when the class itself is processed static { console.log('C's static block'); } }\n
- In CSS properties, flex-basis and flex now implement the keywords content, min-content, max-content, and fit-content for more flexible management of the main area size in Flexbox.\n
- The CSS property scrollbar-gutter has been added to manage the screen space reserved for the scrollbar. For instance, when scrolling content is not needed, it can expand the output and occupy the area of the scrollbar.\n
- An API Self Profiling has been added, implementing a profiling system that allows for measuring JavaScript execution time on the client side to debug performance issues in JavaScript code without manual interventions in the web developer interface.\n
- After removing the Flash plugin, it was decided to return empty values in the navigator.plugins and navigator.mimeTypes properties, but it turned out that some applications used them to check for the presence of plugins for displaying PDF files. Since Chrome has a built-in PDF viewer, the navigator.plugins and navigator.mimeTypes properties will now return a fixed list of standard plugins and MIME types for viewing PDF \u2014 'PDF Viewer, Chrome PDF Viewer, Chromium PDF Viewer, Microsoft Edge PDF Viewer, and WebKit built-in PDF.'\n
- Improvements have been made to the web developer tools. Devices Nest Hub and Nest Hub Max have been added to the device simulation list. A button has been added in the network activity inspection interface to invert filters (for example, when setting the filter 'status-code: 404', you can quickly view all other requests), and there is now the ability to view raw values of the Set-Cookie headers (allowing for assessment of incorrect values removed during normalization). The sidebar in the web console has been deprecated and will be removed in an upcoming release. An experimental feature has been added to hide issues in the Issues tab. Language selection has been added to the settings.
![\"Release](\"\/wp-content\/uploads\/2021\/09\/0199201d43db52675cad778e1add792b.png\")
<\/center> <\/ul>\n