Re: ECMA TC 39 / W3C HTML and WebApps WG coordination

Maciej Stachowiak:
> > Now, there may be pragmatic reasons for avoiding catchall getters and
> > setters:
> > …

Mark S. Miller:
> Yes. As an obvious example of #3, what happens when a Storage
> <> key is "toString"?

It’s a good example of something that’s not obvious, though it is
defined.  If [OverrideBuiltins] is on the interface, then toString is
taken as a a named property; otherwise, it’s the property from the
Storage prototype object.  This is handled by the host object [[Get]]

Cameron McCormack ≝

Received on Saturday, 26 September 2009 05:42:35 UTC