Re: [whatwg] Setting innerHTML to null or undefined

2007-06-05 Thread Maciej Stachowiak
On Jun 4, 2007, at 7:52 PM, liorean wrote: On 05/06/07, Maciej Stachowiak [EMAIL PROTECTED] wrote: I think DOM properties (and sometimes methods and function arguments) vary on this. Some use the raw ECMAScript ToString algorithm. Others additionally map the null value to the empty string

Re: [whatwg] Setting innerHTML to null or undefined

2007-06-05 Thread liorean
On 05/06/07, Maciej Stachowiak [EMAIL PROTECTED] wrote: Actually, it's important for compatibility and conformance with past specs to throw INDEX_SIZE_ERR for some (but not all) properties specced as taking unsigned but actually passed a negative value. On Jun 5, 2007, at 6:29 AM,

Re: [whatwg] Setting innerHTML to null or undefined

2007-06-04 Thread liorean
[Sorry for the double of this post to those who are members of both public-html and public-webapi] On 02/06/07, Anne van Kesteren [EMAIL PROTECTED] wrote: For .innerHTML = null Opera and Internet Explorer act as if the literal string null was used. Firefox acts as if was used. For .innerHTML