W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [WebIDL][Selectors-API] Stringifying null for DOMString attributes and properties

From: Cameron McCormack <cam@mcc.id.au>
Date: Tue, 31 May 2011 17:09:41 +1200
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <20110531050941.GD6179@wok.mcc.id.au>
Lachlan Hunt:
>   WebIDL currently specifies in the ECMAScript to IDL type mapping
> [1] that null stringifies to "null" by default, unless otherwise
> specified with [TreatNullAs=EmptyString].
> Recently, in order to resolve a site compatibility issue caused by
> us stringifying to "null" for some properties, we made all DOMString
> APIs consistent in their handling of null, such that they now
> stringify to an empty string.  We believe this is compatible with
> other implementations for all other attributes and properties that
> we are aware of.
> But this fix also had the result of changing the way we handled null
> in selectors-api, for which we used to stringify as "null".
> I've been informed that Cameron has plans to update WebIDL to make
> this the default too, but hasn't yet done so.

FYI, I made that change yesterday.

Cameron McCormack ≝ http://mcc.id.au/
Received on Tuesday, 31 May 2011 05:10:12 UTC

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