Re: [csswg-drafts] [selectors] Solve :visited once and for all

@astearns @yoavweiss: to the point about the cost and breakage, when I designed this "directed visitedness" approach a few years back (a side-effect of Intersection Observers), the research plan called for quantifying the size of the potential breakage. Several factors we discussed could affect this:

 * what % of sites mark `:visited` links the same colour as `:link` or `:active`? Engines should be able to detect this and report back. The fraction of links coloured this way will be unaffected, subtracting from the impact of the change
 * what fraction of forward navigations are to visibly differentiated `:visited` links that are *not* in the same back-forward navigation chain? That is, what faction of the time do users rely on `:visited` to re-visit sites at some time in the future from their original back/forward clicking?

The last one is hard to reason about. A thorough analysis will require user studies to understand if `:visited` is frequently used in the negative sense: users relying on it to avoid re-visiting sites they've already seen.

I suppose an apology is in order: I had intended to start this work several years ago but didn't, leaving us with relatively little information to attack the problem with today.

-- 
GitHub Notification of comment by slightlyoff
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3012#issuecomment-412530524 using your GitHub account

Received on Monday, 13 August 2018 14:07:40 UTC