Google Chrome 80 stable release, Cookie security settings and automatic blocking of notifications, JavaScript notation etc. will be updated
Version 80.0.3987.87, the latest stable version of the web browser ' Google Chrome ', has been released.
Chromium Blog: SameSite Cookie Changes in February 2020: What You Need to Know
https://blog.chromium.org/2020/02/samesite-cookie-changes-in-february.html
New in Chrome 80: Module Workers, Optional Chaining, New Origin Trials, and more!-YouTube
SameSite Cookies-Chrome Update-YouTube
◆ Standard settings of cookies are changed
It was previously possible to specify the scope of the cookie using the attribute SameSite, but if you do not specify the SameSite attribute, the standard setting is 'Send a cookie when called from any site' As a result, developers who were satisfied with the proper operation of the site often left security risks.
From Chrome 80, the standard setting has been changed to `` Send a cookie when called from a site of the same domain '', it is necessary to appropriately specify the SameSite attribute to send a cookie to a site of another domain there is. However, this change will not be applied immediately after the Chrome update, but the scope of application will gradually spread to all users while checking the scope of influence with a small number of users.
To verify that your site works properly, enter 'chrome: // flags' in the address bar to open the experimental feature settings page, and open 'SameSite by default cookies' and 'Cookies without SameSite'. Enable 'must be secure' and click 'Relaunch' to restart Chrome.
Then go to the site you want to verify and open the developer tools with 'Ctrl + Shift + i'. If there is an error, it will be displayed on the console and you can check the blocked cookies by opening the communication you want to verify on the network tab and checking 'show filterd out request cookies' on the 'Cookies' tab.
◆ Notification request popups that impair the user experience are now automatically blocked
When you visit a website, you may see a pop-up requesting permission to notify you immediately, which is detrimental to many user experiences. From Chrome 80, notifications will be automatically blocked for 'users who block most notifications' or 'notifications blocked by most users'. It is said that this change will also be applied by gradually expanding the target from some users.
◆ Optional chaining notation introduced in JavaScript
When accessing a nested object of JavaScript, an error occurs when the parent object is undefined or null, and code execution stops there, so when accessing an object that is separated by multiple generations, error handling becomes complicated Had become.
Chrome 80 introduces optional chaining notation. Using this notation, if an undefined object is found in the middle, it will stop evaluating after that and return undefined, making it easier to handle objects with deep nesting.
Optional chaining is now ECMAScript's proposal for Stage 4, and it's a step closer to official adoption as it's implemented in Chrome.
◆ Other
SVG images can now be used for favicons, and FTP can no longer be used on non-enterprise clients.
Chrome 80 also includes 56 security bug fixes .
Related Posts:
in Software, Posted by log1d_ts