Mark S. Miller wrote:
Does the [[Overridable]] you have in mind also fix the override
mistake? It sounds like it should.
Yes, definitely.
Regarding shadowable, is there any better documentation than the
doc-comment:
|/*|
| * For ES5 compatibility, we allow properties with PropertyOp-flavored|
| * setters to be shadowed when set. The "own" property thereby created in|
| * the directly referenced object will have the same getter and setter as|
| * the prototype property. Seebug 552432.|
| */|
Is there any observable effect of shadowable? Example?
The comment is a bit misleading. The compatibility at stake is old
SpiderMonkey C API, by which the DOM can make pseudo-data properties
that have native (C function) get and set accessors, but which should
appear to be overridable (as data properties are, if writable). I'm not
sure if I wrote "ES5" there or someone else did, but ES5 helped
straighten out old internal/pre-standard SpiderMonkey interfaces, and
collided under the hood with the pseudo-data property support.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
