https://codereview.appspot.com/247900043/diff/1/src/com/google/caja/es53.js
File src/com/google/caja/es53.js (right):
https://codereview.appspot.com/247900043/diff/1/src/com/google/caja/es53.js#newcode721
src/com/google/caja/es53.js:721: if (fn.ok___ &&
fn.hasOwnProperty('ok___')) { return fn; }
I no longer remember specifically how ok___ was set up. But if it is
like a lot of ES5/3's other markings, then its value is already the
object that it is own on, precisely to make such own property checks
cheap. So if we do want this to be an own property check, and if ok___
does work this way, then was can do simply
if (fn.ok___ === fn) {
As for whether we want this to be an own property check, I also am
curious what Mike Stay has to say. Mike?
https://codereview.appspot.com/247900043/diff/1/src/com/google/caja/es53.js#newcode2633
src/com/google/caja/es53.js:2633: // native ES5 accessors.
Have we actually encountered this as an issue? How? If ES5/3 co-exists
with native accessors, I suspect we have other problems as well. It was
written assuming not.
https://codereview.appspot.com/247900043/
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
