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

Re: [selectors-api] Stringifying undefined

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 18 Feb 2009 16:34:43 +0100
To: "Lachlan Hunt" <lachlan.hunt@lachy.id.au>, "Rune Lillesveen" <rune@opera.com>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.upjz7vpe64w2qv@unknown-00-1d-4f-fa-48-ab.lan>
On Wed, 18 Feb 2009 15:05:42 +0100, Lachlan Hunt  
<lachlan.hunt@lachy.id.au> wrote:
> [...] We have a number of options:
>
> 1. null -> "null", undefined -> "undefined"
> 2. null -> "", undefined -> "undefined"
> 3. null -> "", undefined -> "" (current spec requirement)
>
> Option #1 is the ECMAScript default, and the default defined by WebIDL.  
>   This is currently implemented by IE8.
>
> Option #2 is currently implemented by Mozilla.
>
> Option #3 is currently implemented by Opera and WebKit.

So ideally what we do here is simply in line with how we plan to make all  
APIs that accept strings work (with exceptions).


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Wednesday, 18 February 2009 15:35:44 GMT

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