In 2010, browsers implemented a fix for CSS history sniffing. It worked for some use cases, but not all. Turns out it is REALLY hard to prevent leaks without breaking powerful features, ie “an open research problem crucial to the future of the Web” ieee-security.org/TC/SP2011/…

May 4, 2019 · 8:32 AM UTC

This tweet is unavailable
Then you should bring it up with one or more browsers. Mozilla has a list for privacy (lists.mozilla.org/listinfo/d…) and Chromium has a list for security (groups.google.com/a/chromium…). /cc @dveditz @mikewest