- From: <bugzilla@jessica.w3.org>
- Date: Fri, 18 Nov 2011 18:36:03 +0000
- To: public-script-coord@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14877 Summary: Define [[Class]] of interface prototype objects Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: WebIDL AssignedTo: cam@mcc.id.au ReportedBy: ayg@aryeh.name QAContact: member-webapi-cvs@w3.org CC: mike@w3.org, public-script-coord@w3.org Currently this is left undefined. Behavior of existing browsers, testing with Node and NodeList, using both String(Foo.prototype) and {}.toString.call(Foo.prototype): IE9 and Opera 12.00: "NodePrototype", "NodeListPrototype" Firefox 11a1: "DOM Constructor.prototype" for Node (old bindings), "Object" for NodeList (new bindings) Chrome 17 dev: "Object" So the reasonable choices for the [[Class]] of Foo.prototype are FooPrototype and Object. FooPrototype appeals to me more, personally, but it makes no real difference as long as it's defined. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 18 November 2011 18:36:09 UTC