- From: Dão Gottwald <dao@design-noir.de>
- Date: Thu, 10 May 2007 13:18:10 +0200
- To: Rene Saarsoo <nene@triin.net>
- CC: public-html@w3.org
Rene Saarsoo schrieb: > > I wrote: >>> Similarly authors can make up their own element <foo>, which >>> might be assigned a meaning in some future spec of HTML. >>> But usually there is no benefit in making up your own elements, >>> and people rarely do it. Similarly do they rarely come up with new >>> values for other attributes with predefined sets of values. >>> Why should it be the case with @role? > > Matthew Raymond wrote: >> I don't think that's the case. While people don't commonly invent new >> elements, they use all sorts of arbitrary values for the |rel| >> attribute, especially for microformats. > > This is quite different from making up your own class names. > If I make up my own class name, there is direct benefit - > I can use it in my CSS file as a class selector. > > When I make up my own @rel value, there is no benefit at all. > Only when there exists some technology, that makes use of > this new @rel value, then will people start using it. You don't need a third-party technology. Analogous to class, you can use client-side scripts and CSS. I'm actually doing that on two sites: a[rel~=extern]:after { content: "\2005" url(link_ext.png); white-space: nowrap; opacity: .7; } --Dao
Received on Thursday, 10 May 2007 11:18:19 UTC