This change is currently being made available to Chrome on desktop only. It also allows developers to define an optional ID to globally identify their PWA. It enables them to register as handlers of custom protocols via the installation manifest to increase discoverability. This related to the Encrypted Media Extensions (EME) W3C specification regarding the Content Decryption Module (CDM).Ĭhrome 96 has some Progressive Web Apps (PWAs) enhancements in tow as well. You can read about the implementation in more detail here but an interesting takeaway is that the Safari WebKit team has responded negatively to the change, saying that it overlaps with its own Long Tasks API, so unless it gets a more coherent picture about how the APIs will tie together, it does not support Google's modification.Ī 'MediaKeySessionClosedReason' is also being added to the MediaKeySession so that the JavaScript player can behave accordingly in case of a session closure due to the user turning down the laptop lid versus a fatal crash due to an error. Google is also introducing an 'InteractionID' to the Event Timing API in Chrome 96 to enable developers to easily collect performance-related information. This is yet another step in the move from HTTP to HTTPS. Additionally, the browser will always connect to websites via HTTPS if it has deployed an HTTPS DNS record. It also features some changes to enhance the privacy in these reporting logs, you can read more about the implementation here. Google is also splitting the reporting cache into distinct per-document and network caches. This is intended to enhance your browsing workflow. Next, Chrome 96 also features a 'back-forward cache' so that you can instantly navigate to your previously visited pages.

The latest implementation is strongly supported by web developers. Google says that this will result in faster copying-and-pasting in most scenarios, and in its own limited testing, it noted improvements of 14x when handling 'very large PNGs'. However, with Chrome 96, this behavior is being modified so that it does not strip away the metadata attached to a PNG. Starting with improvements to the Clipboard, the API currently sanitizes PNG metadata that it reads. Today, Chrome 96 has hit the Stable channel with improvements to the Clipboard API, a faster cache mechanism, and more.

Chrome 96 is rolling out with faster page navigation cache and PNG metadata in Clipboardįour weeks ago, Chrome 95 became generally available with enhancements to user-agent (UA) client hints, limits on cookie sizes, and removal of FTP support.

Import export cookies firefox