Google Chrome - News, Updates & Discussions

[Bapun]

Google Chrome Update: SameSite Cookies

Source

From Chrome 80, as part of a staged rollout, the default behavior of cookies will be changing. Cookies without a SameSite attribute will be treated as if they had SameSite=Lax set, which will restrict them to first-party only. Cookies for third-party contexts must be marked with SameSite=None; Secure. Enable this behavior in Chrome now and start testing your sites to make sure you’re ready for the change!

SameSite Cookie Changes in February 2020: What You Need to Know

 

[sumitroy]

Google Chrome updated to version 80.0.3987.87

 

[Rajkumar]

Thank You Sumit Bro, after above pic, I now the process how to update Chrome

 

[Bapun]

Starting in Chrome 82 (to be released April 2020), Chrome will gradually start warning on, and later blocking, these mixed content downloads. File types that pose the most risk to users (e.g., executables) will be impacted first, with subsequent releases covering more file types. This gradual rollout is designed to mitigate the worst risks quickly, provide developers an opportunity to update sites, and minimize how many warnings Chrome users have to see.

Protecting users from insecure downloads in Google Chrome

 

[Siva]

Mac pro performance test with Chrome tabs.

One Chrome tab can kill a Mac. Watch what 6,000 do to a Mac Pro

 

[yashwanth05852]

 

[Sparker0i]

Chrome duet is now rolling out officially on Android

 

[Bapun]

Chrome 80 update cripples top cybercrime marketplace | ZDNet

 

[Bapun]

Chrome updated to Version 80.0.3987.149

 

[sumitroy]

Google Groups

This is an update on our earlier decision to pause our branch and release schedule. As we adapt our future milestone schedules to the current change in schedule, we have decided to skip the M82 release to ensure we keep users safe and focus all efforts on maintaining stability.

Here are some of the immediate actions based on the above decision:

• We will abandon current M82 branches, remove infra support, and stop testing/merges to the branches
• We will not push any new M82 releases to Dev, and we will stop stabilization for Beta
• We will move Dev channel to M83 asap
• We will keep Beta channel on M81 until M83 is ready to be promoted

Once M81 is cleared to release to Stable, we expect to adjust our future milestone schedules, including possibility shifting M83 forward to target an earlier branch and Stable date.