Four weeks ago, Google Chrome 101 was officially released. A month later, this means that it is time for chrome 102 to enter a stable channel. This version features a series of developer related enhancements to the back-end API, abolishes some other APIs, and provides window control coverage for progressive Web Applications (PWA) on the desktop.
A key feature of this release is that developers can control more space in desktop PWA. This is achieved by allowing the client application to expand and control the entire screen. The so-called window control can be understood as the close, maximize and minimize buttons on the title bar. This will make PWA look more like a local application.
You can read more about implementation here:
Similarly, PWA network applications will also be able to act as file handlers with specific MIME types and extensions. If developers modify their PWA list to enable this behavior, they will also see that their network applications are listed in the context menu of "open with...".
A new navigation API has also been introduced, which will meet the needs of single page applications (SPA) because of the existing window The navigation API is a bit complicated for the use of these types, and it is clear that the developers' response to this is "very positive".
The capture processing mechanism has completed its origin experiment and has been widely available. It enables PWA applications to choose to expose control and information to applications undergoing video capture. For example, a video conferencing application can be integrated with a presentation tab to expose controls to navigate slides, which is once again appreciated by developers.
Mozilla has provided a new feature for audio and video streaming, which can be used to estimate the delay. At the same time, the sanitizer API will make it easier to build XSS free applications.
Chrome 102 includes the V3 version of the secure payment confirmation API. It now has two more optional inputs and another necessary one, which means that this is a breakthrough change. Web developers can also use an option to pre filter out devices that do not lead to a friendly user experience through browser pickers. The newly released browser also packs a new surface for origin private file system (OPFS). Here is Google's description of it.
Origin private file system (OPFS, part of the file system access API) has been added with a new surface, which brings high-performance access to data. This new surface is different from the existing surface. It provides local and exclusive write access to the file content. This change, coupled with the ability to continuously read unrefreshed modifications and the availability of synchronous variants on dedicated workers, has greatly improved performance and released new use cases. Our goal is to provide developers with flexibility by providing common, simple and high-performance primitives, on which they can build higher-level storage components. The new surface is particularly suitable for wasm based libraries and applications that want to use custom storage algorithms to fine tune execution speed and memory usage.
Web application authors can also take advantage of two attribute enhancements: inert and until found. Some functions that have completed the origin experiment and are generally available include network state partitioning, inference rules and sub resource loading using network binding.
You can read the details of all these functions here:
In terms of developer experiments, chrome 102 introduces the full screen companion window, the opaque response blocking (ORB) implemented by Google for the first time, and the ability to explicitly block rendering by inserting "blocking = render" as an attribute in scripts and link HTML tags.
Finally, there are two discard and delete changes that need attention, paymentrequest The show() method cannot be called by a website without user activation. This change is to prevent the abuse of malicious websites. Apple Safari browser has done this, while Firefox does not implement the paymentrequest class at all. Second, the "plan B" implementation of the session description protocol (SDP) used when establishing a webrtc session is being removed because it is not cross browser compatible.
Chrome 102 will be available later today. If you don't automatically update to version 102 during the day, please go to help & gt; "About Google browser", once there is an update, you can trigger it. Next comes chrome 103, which will enter the test channel on May 26 and land in the stable channel on June 21.