Re:Purge site data when site identified via old tracking coo...
by ficklepickle on Thursday March 05, 2020 @05:01PM
(#22498823)
Disabling CSS :hover and :active states might break sites. Tracking pixels could be as simple as a background image set for either of those CSS states.
[ Parent
| on HN ]
Re:Purge site data when site identified via old tracking coo...
by matheusmoreira on Friday March 06, 2020 @12:01AM
(#22501111)
Browsers could disable downloading of external resources for CSS :hover and :active. When the user interacts with the interface, the CSS will still get applied but the tracking URL won't be accessed.
Re:Purge site data when site identified via old tracking coo...
by moring on Friday March 06, 2020 @02:28AM
(#22501647)
Alternatively, such URLs can always be pre-fetched on page load.
Re:Purge site data when site identified via old tracking coo...
by JMTQp8lwXL on Thursday March 05, 2020 @06:09PM
(#22499368)
Agreed, but it would likely break things that don't matter much to me. A well defined semantic document should say what it has to say, without the use or necessity of :hover or :active states.
Re:Purge site data when site identified via old tracking coo...
by GoblinSlayer on Friday March 06, 2020 @07:10AM
(#22502958)
Turned off javascript is more about usability than tracking prevention.