You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 21, 2021. It is now read-only.
My use case is that I want to be able to block cookies in "www.google.com" but I want also to be able to allow cookie access in "https://www.google.com/mapsXXXXXXXXXXX".
So when searching google.com, google can't see my cookies, but in maps it can so it'll load all my saved places etc.
This wouldn't be an issue if google had simply built it as a subdomain like "maps.google.com" but it uses a path instead.
The text was updated successfully, but these errors were encountered:
I'll guess that this has been used before.
My use case is that I want to be able to block cookies in "www.google.com" but I want also to be able to allow cookie access in "https://www.google.com/mapsXXXXXXXXXXX".
So when searching google.com, google can't see my cookies, but in maps it can so it'll load all my saved places etc.
This wouldn't be an issue if google had simply built it as a subdomain like "maps.google.com" but it uses a path instead.
The text was updated successfully, but these errors were encountered: