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: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 9 May 2011 13:31:24 -0700
Message-ID: <BANLkTinm-+bLt=SCVGMcGoAG35xZP+PSLQ@mail.gmail.com>
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Cc: public-webapps@w3.org
On Mon, May 9, 2011 at 9:22 AM, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote:
> On 2011-05-07 16:03, Lachlan Hunt wrote:
>>
>> (I don't have results for IE yet because the testharness script I used
>> to write the tests doesn't work in IE.)
>
> I've now tested IE9, which did give me results.  The following properties
> are all stringified to "".
>
> * BODY .text, .bgColor, .link, .vLink, .aLink
> * HR .size
> * A, AREA .coords, .shape
> * IFRAME .width, .height, .marginHeight, .marginWidth
> * TABLE .bgColor, .width
> * COLGROUP, COL .width
> * TR .bgColor,
> * TD, TH .bgColor, .height, .width
> * INPUT .height, .width
> * BUTTON .type
> * .textContent on everything
>
> Every other tested property on HTML*Element interfaces stringified to
> "null".

What about namespaceURI, in various APIs (DOM-Core, DOM-XPath).

In general, my main priority is that we make things as consistent as
possible. My second priority is that we make things follow JS
behavior. So I'd be very happy if we can get away with making the just
the above list stringify to "", and the rest of the DOM stringify to
"null".

/ Jonas
Received on Monday, 9 May 2011 20:32:22 GMT

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