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

Re: Ideas for the ACSS module of CSS3

From: Simon St.Laurent <simonstl@simonstl.com>
Date: Fri, 13 Oct 2000 09:12:23 -0400
Message-Id: <200010131309.JAA05438@hesketh.net>
To: www-style@w3.org
At 05:44 AM 10/13/00 -0700, Ian Hickson wrote:
>On Fri, 13 Oct 2000, Sean Palmer wrote:
>> 
>> Exactly. The reasoning behind it is that a User Agent specific link
>> (or similar), like 'Do you want to hear this damn navigation bar
>> again?' could be placed before the damn annoying navigation bar. It
>> follows on from the WAI WCAG accessibility guidelines (actually HTML
>> Techniques for...):
>> http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20000920/#group-bypass
>> "13.6 Group related links, identify the group (for user agents), and,
>> until user agents do so, provide a way to bypass the group. [Priority
>> 3] " However, the retaining of IDs sounds interesting.
>
>Ah, I see. So what you really want is a way to specify that an element
>contains a common set of links.
>
>(I would personally say that the HTML <link> element would be better
>suited to that, but whatever.)

And I'd point folks to XLink:
http://www.w3.org/TR/xlink/

Bringing it back to CSS, I'd suggest that there's a lot in XLink which CSS
isn't prepared to handle right now, and probably should.

(Of course, some of that might involve behaviors!)

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
XHTML: Migrating Toward XML
http://www.simonstl.com - XML essays and books
Received on Friday, 13 October 2000 09:09:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:06 GMT