4 ms·
Assuming that stuff like this will eventually become common in the ongoing tracking/blocking arms race, I wonder how long it will be before privacy-oriented bro
by smichel17 6y ago
Assuming that stuff like this will eventually become common in the ongoing tracking/blocking arms race, I wonder how long it will be before privacy-oriented browsers/extensions start blocking stuff like :hover pseudo-classes (or eagerly loading all assets).
- lawik 6y agoI'm sure this is already in use but maybe not as published because it is mostly a corner-case (non-JS users). Browsers have already had to implement lies in pseudo-classes, specifically :visited since it leaks too much data.
- chrismorgan 6y agoI can definitely imagine Firefox’s privacy.resistFingerprinting mode starting to block remote resource loading via :hover et al. It’s possible it already does, but I haven’t tested it and find no mention of it. It does several other things that break the occasional site, this would be much the same. But on reflection, it’d be more than that: anything that’s hidden (within `display: none`) and gets shown on hover… hmm. Guess it’d need to ignore `display: none` in deciding to at least fetch the resources, or suffer weird “why is this not loading the background image?” complaints.