- From: Travis Leithead <travil@windows.microsoft.com>
- Date: Thu, 17 Apr 2008 15:06:21 -0700
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- CC: public-webapi <public-webapi@w3.org>
Ok, I think this feedback has been good and productive. With the relative agreement here on the list, I think I will modify the current :link/:visited mitigation to match the proposal here: Selectors that include :link will match all hyperlinks whether visited or not, and Selectors that include :visited will match nothing. As was previously stated, this ensures the following selector will retrieve all links regardless of the UA: ":link, :visited" -Travis -----Original Message----- From: Lachlan Hunt [mailto:lachlan.hunt@lachy.id.au] Sent: Wednesday, April 16, 2008 4:17 PM To: Travis Leithead Cc: public-webapi Subject: Re: [selectors-api] Handling :link and :visited Pseudo Classes Travis Leithead wrote: >>> what is wrong with treating all links as unvisited as far as >>> these APIs are concerned. > > This is the alternate option I'd prefer, if you insist on changing > the spec in this way. However, my first choice would be to not alter > the spec :) I only want to alter the spec to prevent loopholes that allow for major interoperability issues. > To recap your proposal: * :link - matches all links (essentially > document.links, but without the href constraint) whether visited or > not In (X)HTML, I believe :link should be equivalent to: "a[href], area[href], link[href]" > * :visited - matches none. > > Is that correct? Yes. Any solution is fine with the condition that every link in the document is matched by either one of :link or :visited. -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
Received on Thursday, 17 April 2008 22:06:48 UTC