W3C home > Mailing lists > Public > www-style@w3.org > October 2006

RE: [selectors] New pseudo-class proposal: ":current"

From: Rainer ┼hlfors <rahlfors@wildcatsoftware.net>
Date: Fri, 13 Oct 2006 12:26:46 -0600
To: "'David Latapie'" <david@empyree.org>, "'Orion Adrian'" <orion.adrian@gmail.com>
Cc: <www-style@w3.org>
Message-ID: <000001c6eef5$2a1ed620$6700a8c0@OUTDOORS.geartrade.com>

How on earth would CSS know that a link points to the current page? We
already know that the URL cannot be used as the identifier, as URLs can be
rewritten (and frequently are), query strings change. Certainly it has to be
an exact match, as any given URL with different arguments passed to it can
open up a completely different page.

Yes, I think it is a great idea. But it cannot work in any real world
implementation. As such, it will never become part of the CSS standard, or
else it would be already.

Don't you think that this was considered way back when :active :hover
:visited and :link were cooked up?

Rainer ┼hlfors

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf
Of David Latapie
Sent: Thursday, October 12, 2006 3:31 PM
To: Orion Adrian
Cc: www-style@w3.org
Subject: Re: [selectors] New pseudo-class proposal: ":current"

Le 12 oct. 06 Ó 14:14, Orion Adrian a Úcrit :

> While you may get some resistance on the name, I love the idea.

This is a good idea, you are right; I don't see why the name should  
be a problem. Current is trans-media, isn't it? Continuous or paged,  
a site is still amgon different section/(web)pages.

A way to prevent clicking on the link for the current page (a loop)  
would be great too, but this is out of scope for CSS (and, anyway, it  
is not that necessary).

Definitely, :current looks like a great idea for breadcrumbs.

http://blog.empyree.org/   U+0F00
Received on Friday, 13 October 2006 18:27:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:26 UTC