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

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

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 17 Apr 2008 12:33:22 -0500
Message-ID: <480789E2.5080000@mit.edu>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
CC: public-webapi <public-webapi@w3.org>

Bjoern Hoehrmann wrote:
>> and IE8b1 doesn't always match the white-papers.
> After some quick tests I am not sure what it does or is supposed to do.


> As for the suggestion that all links must match one or the other, that
> would disallow e.g. reporting accurate results for all "visible" links
> but omitting any invisble link.

Maybe I'm missing something.  We have two sets of links: S and T.  For links in 
set S, we do not want to communicate their visited status to the script.  For 
links in set T, we're OK to communicate the visited status.  I'm suggesting that 
links in set S should all match :link and not match :visited, while links in set 
T should match depending on their visited status.

A simple implementation that doesn't worry about security has S being the empty 
set and T being all links.  An implementation that doesn't want to hand out any 
history information puts all links in set S.  It sounds like you propose putting 
all "invisible" links in set S.

Do you have a concern not addressed by this approach?

> (As an aside, IE8 throws if the selector argument has trailing white
> space, but does not if it's leading white space instead. A quick reading
> of css3-selectors suggests white space on either end is illegal).

Interesting.  My first-cut implementation in Gecko allows both leading and 
trailing whitespace, more or less as a consequence of reusing the existing CSS 
selector parsing, which allows whitespace around selector lists.  It sounds like 
this might need to be explicitly specified (with tests in the test suite, etc).

Received on Thursday, 17 April 2008 17:34:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:26 UTC