W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2011

[Bug 14877] Define [[Class]] of interface prototype objects

From: <bugzilla@jessica.w3.org>
Date: Sun, 20 Nov 2011 16:06:43 +0000
To: public-script-coord@w3.org
Message-Id: <E1RS9ul-0007lX-BG@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14877

--- Comment #6 from Aryeh Gregor <ayg@aryeh.name> 2011-11-20 16:06:41 UTC ---
Per comment 3, FooPrototype makes the most sense to me.  Descriptive
stringification is better.

(In reply to comment #4)
> If you standardize anything other than "Object", it will be impossible for
> implementations written in JavaScript (like this one:
> https://github.com/andreasgal/dom.js) to conform, at least in ES5.  

You can mostly fake it by adding a custom toString, no?  That doesn't work if
someone uses Object.prototype.toString, but it works for alert().

-- 
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 Sunday, 20 November 2011 16:06:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC