2011/9/24 David Bruant david.bru...@labri.fr
Yet, I still think that not having at the object-level the equivalent of
what we can do at property-level (with getter/setters changing things
based on the receiver object) would be a miss.
Would it really? Javascript data properties are currently
Le 26/09/2011 14:35, Tom Van Cutsem a écrit :
2011/9/24 David Bruant david.bru...@labri.fr
mailto:david.bru...@labri.fr
Yet, I still think that not having at the object-level the
equivalent of
what we can do at property-level (with getter/setters changing things
based on the
On Sep 23, 2011, at 11:18 AM, David Bruant wrote:
My intuition is that WebIDL imposes getter/setters since it is the only
way in ES5.1 to have a per-instance behavior while intuition would
rather be to describe all properties as regular data properties which is
what all these getter/setters
Le 24/09/2011 22:49, Brendan Eich a écrit :
On Sep 23, 2011, at 11:18 AM, David Bruant wrote:
My intuition is that WebIDL imposes getter/setters since it is the only
way in ES5.1 to have a per-instance behavior while intuition would
rather be to describe all properties as regular data
Hi David,
Even without a |receiver| parameter, a Proxy used as a prototype could still
access the receiver for accessor properties and function-valued data
properties (cf. the last code snippet at
http://wiki.ecmascript.org/doku.php?id=strawman:proxy_drop_receiver)
Of course, it would not work
Le 23/09/2011 17:45, Tom Van Cutsem a écrit :
Hi David,
Even without a |receiver| parameter, a Proxy used as a prototype could
still access the receiver for accessor properties and function-valued
data properties (cf. the last code snippet at
Hi,
I recently filed a bug on Firefox [1] regarding the fact that i find the
prototype chain of event objects to be messy (half of the problem is
Firefox specific, the other half is standard as per WebIDL). In this
page [2], click anywhere to see a click event prototype chain (top-left
object is
7 matches
Mail list logo
