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

Re: [selectors-api] Use case for passing invalid selector

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 9 Dec 2008 13:22:05 +0000 (UTC)
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Cc: Simon Pieters <simonp@opera.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.62.0812091320400.30197@hixie.dreamhostps.com>

On Tue, 9 Dec 2008, Lachlan Hunt wrote:
> >
> > # The caller must pass a valid group of selectors.
> 
> The whole point of including the statement is to define what valid input 
> is permitted for the method to work without throwing an exception.  It 
> doesn't prevent authors from passing invalid selectors anyway, and just 
> because they may have a perfectly good reason to do so, doesn't make the 
> input itself valid.

The statement in the spec says that they're not allowed to pass invalid 
selectors, which means that in the case Simon mentioned, you are requiring 
that authors check that the selector is valid before passing the selector 
in. Removing this line doesn't make the selector valid; the selector spec 
already defines what is valid and what is not.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 9 December 2008 13:22:47 GMT

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