Leaking browser history
Leaking browser history
Posted Jun 26, 2008 13:31 UTC (Thu) by Jonno (subscriber, #49613)In reply to: Leaking browser history by jwb
Parent article: Leaking browser history
There is one solution to this problem that would not break the DOM model, but it would introduce a loss of (minor) functionality. The browser simply don't set the 'visited' pseudoclass to any links! That means all links looks like they are unvisited, both in the UI and for any scripts. So the user looses the usual visual clue to whether a link has already been visited but gains some privacy.
