- From: Robert Koberg <rob@koberg.com>
- Date: Thu, 23 Oct 2003 09:02:33 -0700
- To: "'Ian Hickson'" <ian@hixie.ch>
- Cc: <www-style@w3.org>
Golden hammer anti-pattern... you even manage to suggest using non-standard approaches... > -----Original Message----- > From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf > Of Ian Hickson > Sent: Thursday, October 23, 2003 8:46 AM > To: Robert Koberg > Cc: 'Tantek Çelik'; www-style@w3.org > > > On Thu, 23 Oct 2003, Robert Koberg wrote: > > > > With CSS, how would you take this XML element: > > <link idref="a1234"/> > > And style it into: > > <a style="internalLink" href="../folder/page.html">page</a> > > That question is meaningless. You are adding semantics, not styling. > > If the <link> element above is in a proprietary language, then it > shouldn't be sent over the wire anyway, it should be transformed on the > server side. > > If the <link> element is in a fictional but well-known standard namespace, > then it would already have the linking semantics, and so it would already > match the :link and :visited pseudo-classes as appropriate. > > In the extreme case, however, it would be possible to do something like: > > link { binding: url(internalLinks.xml#link); } > > ...where internalLinks.xml is a BECSS binding that defines how elements > should be turned into links. (BECSS is still in development, though. At > the moment, you would use -moz-binding or behavior depending on whether > you were targetting Mozilla or WinIE.) > > > > Or this element: > > <submit servlet="login"/> > > Into: > > <form id="loginForm" action="login" method="post"> > > ... > > </form> > > The same arguments and solutions apply here. > > > > Or, using CSS, turn the things above (or anything) into a PDF? > > There are several CSS-to-PDF systems available. > > -- > Ian Hickson )\._.,--....,'``. fL > U+1047E /, _.. \ _\ ;`._ ,. > http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 23 October 2003 12:02:35 UTC