- From: Brendan Eich <brendan@meer.net>
- Date: Tue, 06 Dec 2005 12:55:29 -0800
- To: www-dom@w3.org
Then, after adoption, IE unilaterally changed it,
This is not so. IE always implemented an odd mixture of nullable string
valued properties and non-nullable string-valued properties (which when
missing are returned as ""), and furthermore mapped properties to
attributes directly, via getAttribute.
So this has everything to do with backward compatibility going back to
IE 4. The Mozilla experiment that you describe was much later, and
suffered the nullability confounder. I just spoke with Johnny Stenback
about this and he said there may have been confusion when testing IE
between nullable and non-nullable attributes mapped from DOM JS properties.
/be
Received on Tuesday, 6 December 2005 20:55:56 UTC