- From: Manuel Strehl <manuel.strehl@stud.uni-regensburg.de>
- Date: Fri, 09 Dec 2005 09:20:55 +0100
- To: "www-style@w3.org" <www-style@w3.org>
Hmm, I think that could be done by
div.xpath( ... ):hover
Some of the advantages of XPath in CSS would be:
- Easier transformation, if you have XPath (e.g., in XSLT stylesheets)
and want CSS applied to it
- usage of XPath functions.
It is true that much will be possible in CSS3, but why invent the wheel
2 times?
Manuel
Christoph Wieser schrieb:
>Hi Manuel,
>
>in most of the cases the translation of CSS-Selectors to XPath
>expressions is rather easy but translating pseudo-classes like :hover or
>:link to XPath turns out to be a problem.
>
>Kind regards,
>Christoph
>
>
>
>Manuel Strehl wrote:
>
>
>>Hi.
>>
>>How about introducing a pseudo-class (for example), that allows
>>selection by using xpath syntax. Most of the common browsers already
>>include a XSLT parser with (more or less) full XPath support, so
>>technically there should be no problem.
>>
>>CSS syntax could be something like:
>>
>>body:xpath( ./div/table ) {} /* == body div table {} */
>>
>>based upon the element carrying the pseudo-class. An expression like
>>*:xpath( /... ) could refer to the document root and allow complete
>>switching to xpath.
>>
>>I DO see that with this proposal I run into conflict with my last
>>posting about "//" comments, but that's life... ;-)
>>
>>Manuel
>>
>>
>>
>
>
>
Received on Friday, 9 December 2005 08:21:07 UTC