batepapo.uol.com.br - site is not usable

[MarcusCorbacho]

URL: https://batepapo.uol.com.br/Cidades-e-regi%C3%B5es/Bahia/S/Salvador/Salvador-(20)

Browser / Version: Firefox 76.0
Operating System: Windows 10
Tested Another Browser: Yes

Problem type: Site is not usable
Description: cookie “SIDCC” will be reject “sameSite” set as “none”
Steps to Reproduce:
Last days I was facing a nasty problem on HBOGO ( #49577 ) although resolved toggle to false network.cookie.sameSite.laxByDefault

Now, on this site, thru information by Console I noticed some new and I don´t know what can be do to resolve.

View the screenshot

Browser Configuration

• None

From webcompat.com with ❤️

[softvision-sergiulogigan]

@MarcusCorbacho thanks for the reported issue!
I think I see the same behavior on Chrome Canary as well. Can you confirm?

[MarcusCorbacho]

@softvision-sergiulogigan Not only Chrome Canary friend... I´ve Tested on All Chrome channels (Canary; Dev; Beta and Release) , Microsoft Edge (Canary; Dev; Beta; and Release) , Firefox (Nightly; Dev; Beta; and Release) all of them on this particular site (maybe others, who knows!) alll of the browsers seeing on Console has this behavior related to Cookie and SameSite.

The only Browser indeed worked, for now, was Firefox ESR ! (But impossible choice for me, as that option not even have Lockwise)

So my question is, why Mozilla and Others, changes theirs browsers related on Cookie Policy stuff, if the Websites are not prepared yet to that change? This change is gona impact a massive websites, and I´m Afraid that will be so many reporting issues related to that.

Even So, as I said before, the workaround toggle to false network.cookie.sameSite.laxByDefault, not worked on this site, now I don´t know what to do.

[karlcow]

From https://web.dev/samesite-cookies-explained/

Cookies are one of the methods available for adding persistent state to web sites. Over the years their capabilities have grown and evolved, but left the platform with some problematic legacy issues. To address this, browsers (including Chrome, Firefox, and Edge) are changing their behavior to enforce more privacy-preserving defaults.

Also w3ctag/design-reviews#373

[karlcow]

what is the issue with the site and what are the steps to reproduce the issue. I see the same behavior in all browsers for now, but without precise steps it will difficult to understand it.

[softvision-sergiulogigan]

I think the issue here is actually the Console putput, especially the "lax" containing ones, like
Cookie “SIDCC” has “sameSite” policy set to “lax” because it is missing a “sameSite” attribute, and “sameSite=lax” is the default value for this attribute.

[karlcow]

Yes it's just a console message, not an issue. :) Pretty much all sites display this right now. :)
Let's close then. We can reopen if there's a difference of behaviors in between browsers. Thanks.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue at https://webcompat.com/issues/new if you are experiencing a similar problem.