W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [selectors-api] Stringifying undefined (was: Call for Consensus - Selectors API to Candidate Rec)

From: Robin Berjon <robin@berjon.com>
Date: Fri, 13 Feb 2009 16:02:27 +0100
Cc: WebApps WG <public-webapps@w3.org>, Rune Lillesveen <rune@opera.com>
Message-Id: <31FCD626-8ECE-46EC-8896-60771E5AF08B@berjon.com>
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>

Hey Lachlan,

thanks for tracking this down.

On Feb 13, 2009, at 14:23 , Lachlan Hunt wrote:
> But now that the NSResolver has been removed, the consistency  
> reasoning no longer really applies.  The benefit to debugging still  
> sort-of does, but it is certainly debatable.

Given that adding NSResolver (or something like it) is potential for  
v2, it might be best to keep the thinking that brought us here from it?

> There are 2 problems with changing the spec now to use the default  
> behaviour instead of defining the empty string:
> 1. We are getting ready to go to PR.  It would be rather annoying to
>   have to hold up this for much longer.  Although I generally don't
>   like letting bureaucratic issues like this get in the way of doing
>   things, if it can be avoided.

I reckon that if it had to be done, given the size of the change you  
could get the major stake-holder to okay the change publicly and still  
go to PR claiming that LC was done through the commenting and that a  
zero-length CR is fine. Hey, it can feel wrong yet be sooo right.

Robin Berjon - http://berjon.com/
     Feel like hiring me? Go to http://robineko.com/
Received on Friday, 13 February 2009 15:03:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:14 UTC