16098 2012-02-24 03:27:22 +0000 callback interfaces with constants should have no interface prototype object 2012-03-01 05:38:14 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified All All RESOLVED FIXED P2 normal --- 1 cam cam annevk bzbarsky mike public-script-coord travil public-webapps-bugzilla oldest_to_newest 64518 0 cam 2012-02-24 03:27:22 +0000 Since there will never be instances of call back interfaces, there's no need for a .prototype property on their interface object (which exists only when there are constants on the call back interface). 64522 1 annevk 2012-02-24 08:00:42 +0000 Is the method not exposed on the prototype? 64523 2 bzbarsky 2012-02-24 08:32:08 +0000 Exposed in what sense? 64570 3 travil 2012-02-24 19:50:40 +0000 This is 100% inline with IE9's behavior, so I'm happy to see this minor change. (At the time, we created an extended attribute to control this, but with 'callback' it's not necessary :) // Introduced in DOM Level 2: [msInterfaceObjectOnly] interface NodeFilter { /* ... */ }; 64808 4 cam 2012-03-01 05:16:39 +0000 Turns out this was already required. The second paragraph in http://dev.w3.org/2006/webapi/WebIDL/#interface-object says "The interface object for non-callback interfaces must also have a property named “prototype” ...". 64809 5 bzbarsky 2012-03-01 05:28:56 +0000 That line doesn't say that callback interfaces _can't_ have such a property (jus that non-callback ones have to), and other places in the spec are written as if that property is never null.... I think it would be good to explicitly clarify this. 64810 6 cam 2012-03-01 05:37:59 +0000 Fair enough, added this sentence below that paragraph: The interface object for a callback interface MUST NOT have a “prototype” property.