> It was a compatibility nightmare when people didn't namespace, and
> when you couldn't make non-enumerable properties.  Using a namespace
> for additions to the prototype chain and using ES5's defineProperty to
> keep those additions from affecting enumeration behaviour seems like
> it overcomes those, at least to me.

Unfortunately not all browsers/environments support ES5
defineProperty, and not all third party code, widgets, ads, and js
libs guard against extensions in their for-in loops.

-JDD
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to