- From: Cameron McCormack <cam@mcc.id.au>
- Date: Wed, 09 May 2012 14:14:00 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: public-script-coord@w3.org
Anne van Kesteren:
> We were wondering what the rationale is for treating undefined identical
> to null in nullable types. The change happened over 10 months ago, but
> there does not appear to be related mailing list discussed.
>
> http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml?f=h;rev=1.295
I think undefined needs to be treated as null, at least with the current
formulations of various DOM operations. Something like:
<!DOCTYPE html>
<body><span>hello </span>
<script>
var n = document.createTextNode("there");
document.body.insertBefore(n, undefined);
</script>
needs to behave the same as insertBefore(n, null).
Received on Wednesday, 16 May 2012 23:40:10 UTC