W3C home > Mailing lists > Public > public-webapi@w3.org > April 2008

[selectors-api] Handling :link and :visited Pseudo Classes

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Wed, 16 Apr 2008 14:12:16 +0200
Message-ID: <4805ED20.6040209@lachy.id.au>
To: public-webapi <public-webapi@w3.org>
Cc: Travis Leithead <travil@windows.microsoft.com>

Hi,
   The current Selectors API draft states:

   "... user agents may treat all links as unvisited links, or implement
    other measures to preserve the user’s privacy."

I have noticed that to address this issue, Microsoft's implementation in 
the current IE8 beta, both :link and :visited pseudo-classes are being 
completely ignored.  That approach would technically fall under "other 
measures to preserve the user’s privacy", but it seems like it could be 
an interoperability issue.

Current WebKit builds and our internal Opera builds don't take any 
action.  Both :link and :visited return unvisited and visted links, 
respectively.  This also appears to be the approach Mozilla are planning 
to take [1].  I think we need to be interoperable with our handling of this.

I'm considering adjusting the spec to allow just two options, and making 
IE8's behaviour non-conforming.

Either:
1. Match unvisited and visted links normally with :link and :visited, 
respecitively.
2. Match all links with :link, and no links with :visted (i.e. treat all 
links as unvisited)

Another option would be to effectively treat :link and :visited as 
synonymous and match all links with both, but I'm not so comfortable 
with that.

Feedback from implementers on this issue, particularly from Microsoft, 
would be appreciated.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=416317#c16

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Wednesday, 16 April 2008 12:12:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 April 2008 12:13:00 GMT