![]() ![]() Chrome users may notice a few changes as well. Unship deprecated "track" and "stream" stats from getStats() (Origin trial)Ĭheck out the website for additional information on these.WebAssembly Garbage Collection (WasmGC) (Origin trial). ![]() ![]() “Reload this page” infobar no longer shown if top-level frame is observing permission changes (behind flag).APIPayment handler minimal header UX (behind flag).FedCM: Auto re-authentication (behind flag).Deprecate non-standard `shadowroot` attribute for declarative shadow DOM (behind flag).Add containerName and containerQuery, update conditionText (behind flag).“Reload this page” infobar no longer shown if top-level frame is observing permission changes.RegExp v flag with set notation + properties of strings.Add optional submitter parameter to FormData constructor.Deprecate the `document.domain` setter.The Chrome Status page for Chrome 112 lists developer related changes for the most part: While that is reassuring, it is still suggested to update to the latest Chrome version as soon as possible to protect the browser against potential attacks targeting the security issues. Google makes no mention of exploits in the wild. They address a wide range of security-related issues, including heap buffer overflow, user after free, out of bounds or insufficient policy enforcement issues. The severity ratings of the issues are high, medium and low. Google lists externally reported security vulnerabilities on the official Chrome Releases website. It addresses 16 different security issues in the web browser. Google Chrome 112 is a security update for all platforms. The following versions should be listed after the update: A restart of the browser is required and the new Chrome version is launched. It should find the new Chrome update, if not installed already, and download it. Chrome users may load chrome://settings/help in the browser's address bar to display the installed version and run a check for updates.
0 Comments
Leave a Reply. |