W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: QSA, the problem with ":scope", and naming

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 18 Oct 2011 17:04:29 -0400
Message-ID: <4E9DE9DD.8030200@mit.edu>
To: Brian Kardell <bkardell@gmail.com>
CC: public-webapps@w3.org
On 10/18/11 5:01 PM, Brian Kardell wrote:
> This too has come up in some discussions on CSS (CSSOM I think) that I
> have had.  In the right context - I don't think it would actually be
> that hard.  It would require a way to provide a sand-boxed evaluation
> (read only elements)

This is not that easy.  Especially because you can reach all DOM objects 
from elements, so you have to lock down the entire API somehow.

> and a pattern much like jquery's where it is a
> filter which can only return true or false.  True enough that it would
> be slower than native for a few reasons - but perhaps still useful.

The slowness comes from not having a way to tell whether the world has 
changed under you or not and therefore having to assume that it has, not 
from the actual call into JS per se.

-Boris
Received on Tuesday, 18 October 2011 21:04:58 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT