A lot of variation among what each #browser offers in #privacymode - is it a bug or a feature? where would more interoperability help? where do we need to leave room for differentiation? @w3ctag is investigating the question github.com/w3ctag/design-rev…
Hadley Beeman @hadleybeeman
31 Jan 2018
I've been doing some research on #privacymode in browsers. (THREAD) Use cases: - To protect you from • the next person to use your browser • the network snooping • the site knowing too much about your prior browsing - For a fresh browsing context (no cookies/fingerprinting)
3
3
We need the ability to set this domain wide that doesn't change the gui. (2/2)
1
Replying to @POWRSURG @w3ctag
Does the Clear-Site-Data help a bit in that direction? It is more meant as a security than privacy feature, so it's probably not enough on its own (e.g. it probably still leaves traces in browsing history). cc @mikewest

Feb 1, 2018 · 8:26 AM UTC

1
Replying to @w3cdevs @w3ctag @mikewest
It sounds like it could help at least. It has been a few years since I worked on the site so it wasn't around then. Ideally you'd also want such a thing done in JS too as a JS redirect would have gotten them off the site faster. Still, a step in the right direction.