- From: Chris Lilley <chris@w3.org>
- Date: Thu, 01 Mar 2001 23:24:01 +0100
- To: Biep Durieux <bdurieux@baan.com>
- CC: "'www-style@w3.org'" <www-style@w3.org>
Biep Durieux wrote: > Chris Lilley <chris@w3.org> wrote: > >To put that question in its correct chronological order, > >why was XPath such a departure from W3C selectors? > > The relevant question is: should one adopt a mediocre solution? Clearly not. > The question is not about what was first, but what is better. If XPath is > good for CSS purposes, by all means let's adopt it, if it is not, don't > let's. OKI. As I said, XPath is lacking specificity, lacking pseudoelements, and lacking pseudoclasses; and its greater generality slows rendering because you can't lay anything out until the complete document has loaded. So, lets not change to an inferior soution (for CSS purposes) without good reason. > CSS started out as a great solution, but what's happening with it is making > me sad. It seems to be deteriorating into another bit of bloatware that > will require knowledge of hundreds of reserved words to understand. I fail to see how you draw that conclusion. -- Chris
Received on Thursday, 1 March 2001 17:24:21 UTC