I like this! No more csrf tokens 😁
I like this one😁
Way to go. Next, please block Canvas/Font/OS/Plugin/Audio/Local Date/JS API fingerprinting (super cookies).
Why "Lax" keyword? Intuitively lax for me is in contrast accociated with something not secure and weak.
1:18 "… let's talk about why you might want to use third party cookies.". Really Google?…
That is great, but increasingly I ask myself does it consulted with W3C/Ecma etc.
Ok, very nice 👍Setting the flags and opening console on this site (youtube) is generating a lot of warnings now… 😁 (Chrome 79)
because of this my memory leaks, see other client. make loop http load.
Why is it mandated to set Secure flag to True when the SameSite is set to None ?
Any idea ?
Big corporations make live of small to be more harder until they died – this is real reason for changes!
Bug Hunters will try harder.
THX Enabled 😛
great to know.
Now it's not available navigation gestures in chrome flags
the best part is Safari and iOS12 treating `SameSite=none` as `SameSite=strict`, and they won't backport the fix from 13 to 12
Firebase auth is triggering these warnings. https://github.com/firebase/firebase-js-sdk/issues/2284
The chrome 80 beta version's 'samesite' flags are defaulted. However, you changed two of them to enabled. Does this mean that when Chrome 80 production version releases, it will have these two flags enabled by default ?
But if you want integrate this movie now with SameSite=none in IIS, it will still never work 🙁 Chrome 80) Chrome the new IE 6 !!?
Are those flags been added to google.font api request? Last time I checked, I still had the warnings –'
You forgot to mention that SameSite=None breaks old browser cookies!
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.