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

2011-05-30 Thread Cameron McCormack
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 so

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

2011-05-10 Thread Lachlan Hunt
On 2011-05-09 22:31, Jonas Sicking wrote: On Mon, May 9, 2011 at 9:22 AM, Lachlan Hunt wrote: Every other tested property on HTML*Element interfaces stringified to "null". What about namespaceURI, in various APIs (DOM-Core, DOM-XPath). Node.namespaceURI is readonly according to DOM3 Core, s

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

2011-05-09 Thread Jonas Sicking
On Mon, May 9, 2011 at 9:22 AM, Lachlan Hunt 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

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

2011-05-09 Thread Lachlan Hunt
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,

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

2011-05-07 Thread Boris Zbarsky
On 5/7/11 10:03 AM, Lachlan Hunt wrote: For document.write(), Gecko, Webkit (including Safari 5), Opera and IE write "null" on both Windows and Mac. I don't know which version of Safari you were using that gave you a different result. I was using Safari 5 on Mac; looks like it does something we

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

2011-05-07 Thread Lachlan Hunt
On 2011-05-06 15:45, Boris Zbarsky wrote: On 5/6/11 6:10 AM, Lachlan Hunt wrote: 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 e

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

2011-05-06 Thread Boris Zbarsky
On 5/6/11 6:10 AM, Lachlan Hunt wrote: This definition matches current selectors-api implementations, which do this conversion for the selectors parameter and this is also the result expected by the current selectors api test suite. However, according to information I got from Anne, and from my o

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

2011-05-06 Thread Lachlan Hunt
Hi, WebIDL currently specifies in the ECMAScript to IDL type mapping [1] that null stringifies to "null" by default, unless otherwise specified with [TreatNullAs=EmptyString]. This definition matches current selectors-api implementations, which do this conversion for the selectors parameter