- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Thu, 20 Sep 2012 15:36:10 -0400
- To: Ryosuke Niwa <rniwa@webkit.org>
- CC: public-webapps <public-webapps@w3.org>, Aryeh Gregor <ayg@aryeh.name>
On 9/20/12 3:25 PM, Ryosuke Niwa wrote: > I guess. The tricky part is that almost all methods and properties on > DOMTransaction are optional. Do you know how one might specify a methods > on a callback interface to be optional? I'm not sure you can, really. But you can specify them to be nullable, and undefined becomes the null value, so you can at least tell apart "null or undefined" and "an actual callable object". Note that I _think_ attempts to use non-callable objects there should throw, in general. But that's not too obvious to me from the specs. :( -Boris
Received on Thursday, 20 September 2012 19:36:40 UTC