Google has published the release of the Chrome 104 browser and the stable release of the Chromium project.
See also: our review of the best laptops for engineering students (August 2022).
Key changes in Chrome 104 include:
- time limit for a cookie. Now all new or updated cookies will be automatically deleted after 400 days even if other Expires and Max-Age attributes are present. Cookies created before this will be saved, but not updated;
- blocking calls from the iframe to URLs referring to the local file system ("filesystem://");
- optimization for faster page loading, which ensures that a connection is established with the target host at the moment the link is clicked;
- settings for managing the user cohorts API by interest as part of the Privacy Sandbox initiative. The corresponding infodialogs will be shown once to explain the essence of the technology to the user and offer to activate its support in the settings;
- increased thresholds (from 5 to 100) to limit nested setTimeout and setInterval timer calls fired with an interval of less than 4ms ("setTimeout(…, <4ms)");
- sending a CORS (Cross-Origin Resource Sharing) authorization request with the header "Access-Control-Request-Private-Network: true" to the server of the main site, if the page accesses a subresource on the internal network (192.168.x.x, 10.x.x.x , 172.16-31.x.x) or to localhost (127.x.x.x). The server should return an "Access-Control-Allow-Private-Network: true" header. So far, the confirmation result does not affect the processing of the request, but simply displays a warning. To enable blocking in earlier releases, you can activate the setting "chrome://flags/#private-network-access-respect-preflight-results";
- the Region Capture mechanism, which allows you to trim excess content from a video generated based on screen capture;
- support for the new media query syntax defined in the Media Queries Level 4 specification with a minimum and maximum size of the visible area (viewport). This allows you to use the usual mathematical comparison operators and logical operators ("not", "or", and "and");
- new APIs in Origin Trials mode;
- "focusgroup" CSS property to improve element navigation using keyboard cursor control arrows;
- the ability for a user to disable the storage of credit card parameters in the Secure Payment Confirmation API. The PaymentRequest() constructor provides the corresponding flag "showOptOut: true";
- Shared Element Transitions API for smooth transition between different views of content in single-page web applications;
- stabilized support for speculative rules so that site authors can send the browser information about the most likely pages that the user can go to;
- a stabilized mechanism for packaging sub-resources into packages in the Web Bundle format in order to increase the efficiency of downloading a large number of accompanying files;
- The object-view-box CSS property to define the part of the image that will be displayed in the area instead of the given element;
- Fullscreen Capability Delegation API so that one Window object can delegate to another object the right to call requestFullscreen();
- Fullscreen Companion Window API to place fullscreen content and popups on another screen after receiving confirmation from the user;
- the visual-box attribute in the overflow-clip-margin CSS properties to determine where to start clipping content that has gone beyond the border of the region;
- the ability in the Async Clipboard API to add definitions of specialized formats for data transmitted through the clipboard, other than text, images, and text with markup;
- support for specifying a color space for the rendering buffer and transformation when importing from a texture into WebGL;
- End of support for OS X 10.11 and macOS 10.12 platforms;
- deprecation of U2F (Cryptotoken) API support.
- Improvements have also been made to the developer tools:
- added the ability to restart the code from the beginning of the function in the debugger;
- added support for developing add-ons for the Recorder panel with visualization of labels set in the application through a call to the performance.measure() method;
Also in Chrome 104, 27 vulnerabilities were fixed.
The next release, Chrome 105, is scheduled for August 30th.
In July, Google released Chrome 103. It included an experimental image editor, autocomplete for credit and debit card numbers, support for the 103 HTTP response code, and more.