W3C home > Mailing lists > Public > www-style@w3.org > July 2013

Re: ITS 2.0, Selectors 4 and Selectors API 2

From: Jirka Kosek <jirka@kosek.cz>
Date: Wed, 03 Jul 2013 14:13:11 +0200
Message-ID: <51D41557.4070100@kosek.cz>
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
CC: "www-style@w3.org" <www-style@w3.org>, public-webapps <public-webapps@w3.org>, public-multilingualweb-lt-comments@w3.org, Felix Sasaki <fsasaki@w3.org>
On 2.7.2013 2:53, Daniel Glazman wrote:

> a. it's not possible, even in Selectors API 2 [5], to resolve arbitrary
>    namespaces in querySelectorAll()

In general this might be problem, but for ITS I don't see this as a
problem. People who use ITS with non-HTML content (various flavours of
XML) will use XPath as a query language. Selectors will be likely used
only in combination with HTML content where you don't need namespaces
(of course, unless you want to target specific elements inside embedded

> b. Selectors cannot target attributes

Indeed, this is very serious limitation of CSS selectors and we even
discussed removing CSS selectors completely from ITS because of this.
But at the end prevailing opinion was that CSS selectors will be useful
for scenarios where there is no need to care about attributes. But
without ability so select attributes some users will be forced to switch
to XPath instead of CSS selectors.


  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
    Bringing you XML Prague conference    http://xmlprague.cz

Received on Wednesday, 3 July 2013 12:13:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC