Justin Schuh, Chrome’s director of engineering, announced in a Chrome blog post that the SameSite cookie feature was temporarily rolled back to ensure the stability of the site during the new coronavirus outbreak. SameSite is a new cookie classification model that was introduced in the Chrome 80 stable released in early February. Chrome will set the default setting for cookies that do not declare the SameSite value as SameSite.Lax.
Only with SameSite-None; The cookies set by Secure can be accessed externally, provided that they are accessed through a secure connection, or HTTPS. It will change the past abuse of user privacy and ensure that cross-site cookies can only be accessed over HTTPS connections.
With this policy, users can disable third-party cookies. At the same time, however, disabling third-party cookies can cause some sites to crash. To that end, Google said, “We want to ensure the stability of websites that provide basic services, including banks, online groceries, government services and healthcare, that can improve our daily lives during this time.” “
Since February, only a handful of users have enabled the SameSite cookie feature, which Google had planned to roll out for the rest of the year for the rest of the year. Schuh says users, organizations, or sites should be undisturbed when rolling back the feature.
The rollback is temporary, and the SameSite cookie feature will be turned on again, and Schuh said it expects to resume this summer.