3 added 86 characters in body
source | link

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a wildcard.

Screenshot of Chrom* Devtools with Application->Cookies selected


This is just a quick workaround. I consider the behaviour a , too.

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a wildcard.

Screenshot of Chrom* Devtools with Application->Cookies selected

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a wildcard.

Screenshot of Chrom* Devtools with Application->Cookies selected


This is just a quick workaround. I consider the behaviour a , too.

2 added 120 characters in body
source | link

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the devtoolsusing the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a wildcard.

Screenshot of Chrom* Devtools with Application->Cookies selected

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the devtools you can change the path to / that causes it to effect the entire domain.

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a wildcard.

Screenshot of Chrom* Devtools with Application->Cookies selected

1
source | link

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the devtools you can change the path to / that causes it to effect the entire domain.