MDN’s new design is in Beta! A sneak peek:

JS object extensions

I'm not sure where to place Mozilla JS extensions such as __noSuchMethod__, __proto__, and __parent__ - should these have root-level pages even though they are properties of objects (but not properties of Object.prototype)? --Maian 23:41, 27 October 2005 (PDT)

I would put them to JS:Object.__proto__. This won't have exactly the same meaning as, say,, but I think it shouldn't confuse the readers if we include an appropriate description on JS:Object page. Perhaps this should be discussed on the list? --Nickolay 05:19, 28 October 2005 (PDT)
On a later thought, it might make sense to put them to JS:Object:__proto__. --Nickolay 14:45, 29 October 2005 (PDT)
Yeah, that makes sense. --Maian 19:44, 30 October 2005 (PST)

object (prototype-)base property

should not the base property be referenced-in/described-under this page or perhaps rather on the function-object page? or have i missed it somewhere? --vike 23:35, 26 March 2007 (PDT)
oh, sorry, after further reading below Details_of_the_Object_Model#More_Flexible_Constructors i believe i had miss-understood the guide and its talk about a base property for to be a reserved/special property - now i think its just a regular variable, right? cant understand why one couldnt call the method directly though...
(ill probably remove this heading if i seem to be more correct in my now later understandings) peace.. --vike 00:16, 27 March 2007 (PDT)

Yes, base is a custom property. The code in the guide can be simplified to the appropriate call. --Nickolay 14:52, 4 April 2007 (PDT)

Document Tags and Contributors

 Contributors to this page: Nickolay, Vike, Maian
 Last updated by: Nickolay,