W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] definition of :link and :visited should allow flexibility

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 3 Aug 2010 00:52:10 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.1008030051220.7470@ps20323.dreamhostps.com>
On Fri, 30 Apr 2010, L. David Baron wrote:
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#selector-link
> says:
>   # All a elements that have an href attribute, all area elements
>   # that have an href attribute, and all link elements that have an
>   # href attribute, must match one of :link and :visited.
> 
> A number of user agents have recently implemented changes to
> handling of :link and :visited that can't be described strictly in
> terms of an element matching a selector.  These are described in
> more detail in http://dbaron.org/mozilla/visited-privacy .
> 
> css3-selectors has an exception that allows this:
>   # UAs may therefore treat all links as unvisited links, or
>   # implement other measures to preserve the user's privacy while
>   # rendering visited and unvisited links differently. 
>     --http://www.w3.org/TR/css3-selectors/#the-link-pseudo-classes-link-and-visited
> 
> HTML5 should have a similar exception that allows user agents to be more 
> flexible than requiring that all of the elements listed match exactly 
> one of :link and :visited.

I've added a paragraph saying that another spec might introduce additional 
requirements here.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 2 August 2010 17:52:10 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:25 UTC