Re: [whatwg] Setting innerHTML to null or undefined

2007-06-04 Thread Michael A. Puls II
On 6/4/07, Jonas Sicking [EMAIL PROTECTED] wrote: Anne van Kesteren 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 = undefined Opera, Firefox and Internet Explorer act as if the literal string

Re: [whatwg] Setting innerHTML to null or undefined

2007-06-04 Thread liorean
On 05/06/07, Michael A. Puls II [EMAIL PROTECTED] wrote: On 6/4/07, Jonas Sicking [EMAIL PROTECTED] wrote: I'd really dislike having to have this one property behave differently than other text properties in the DOM. How do opera/ie deal with other text properties like .src, .id,

Re: [whatwg] Setting innerHTML to null or undefined

2007-06-04 Thread Maciej Stachowiak
On Jun 4, 2007, at 5:45 PM, liorean wrote: On 05/06/07, Michael A. Puls II [EMAIL PROTECTED] wrote: On 6/4/07, Jonas Sicking [EMAIL PROTECTED] wrote: I'd really dislike having to have this one property behave differently than other text properties in the DOM. How do opera/ie deal with

[whatwg] Setting innerHTML to null or undefined

2007-06-02 Thread Anne van Kesteren
For .innerHTML = null Opera and Internet Explorer act as if the literal string null was used. Firefox acts as if was used. For .innerHTML = undefined Opera, Firefox and Internet Explorer act as if the literal string undefined was used. -- Anne van Kesteren http://annevankesteren.nl/