Google will temporarily reset the cookie requirements for Chrome’s SameSite cookie


Google will temporarily reset the cookie requirements for Chrome's SameSite cookie

With the launch of Chrome 80 in February, Google gradually began rolling out an update that changes how third-party cookies work on websites called “SameSite”. Today, announced it that it is temporarily reversing these SameSite requirements in light of the COVID-19 outbreak.

The SameSite policy was a change in the way Chrome handles cookies. Previously, Chrome accepted more cookies by default, including from third parties. SameSite has reversed that by default. At a high level, this essentially means that Chrome will block it unless a third-party cookie is explicitly set by a website owner. This step was designed to protect the privacy of users by limiting which cookies can function in a third-party context, which would supposedly limit third-party data collection.

However, disabling third-party cookies can cause some sites to break, especially if they use third-party cookies as part of their login systems. Many major sites have already been updated to take SameSite into account, but Google says it “wants to ensure stability for websites that provide essential services, including banking, online shopping, government services, and healthcare.” That presumably means that some sites in those categories have not been updated.

Because sites have faced the complications caused by the COVID-19 outbreak, many likely have not had the time or the means to adapt to the update and will likely not be able to focus on it in the near future .

Since social distance measures have greatly increased dependence on online services, such distortions can pose a number of problems, especially when linked to health care sources.

This isn’t the only Chrome update affected by the outbreak. In March, Google announced that it would temporarily stop adding new features to Chrome and Chrome OS and focus on security-related updates. Google said this was due to changes in its own work schedules. Google does, however since resumed development for Chrome and Chrome OS, albeit on a custom schedule.