Per-Erik Brodin: > The DOMString arguments 'options' and 'configuration' are never > referred to as being null, and thus I think it is safe to assume > that they will not be null and that the default conversion rules > apply (http://dev.w3.org/2006/webapi/WebIDL/#es-DOMString). The > callback arguments are all referred to as being null so I think it > is safe to assume that they can be null. Interface types now *do not* include null as one of their values unless you make the type nullable explicitly. The HTML spec hasn?t been updated for this yet, though I have written a patch to do so: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10640 -- Cameron McCormack ? http://mcc.id.au/Received on Monday, 13 June 2011 15:32:35 UTC
This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:33 UTC