archives

« Bugzilla Issues Index

#2788 — 26.2.3.7.1 Reflect.Realm.prototype.directEval: Type checks don't match NOTE


26.2.3.7.1 Reflect.Realm.prototype.directEval ( source )

Steps 1-4 check the thisValue type, but according to note, thisValue is always `undefined`.


I think the note is refering to how the directEval hook is called as part of the implementation of direct eval. However, the actual method on Realm.prototype could be called by anybody with any this value.

The realm question is probably whether these specific methods (directEval, indirectEval, nonEval) have any dependencies upon the associated Realm object being initialized. The default directEval clearly doesnn't and nonEval also doesn't seem to need it. indirectEval appears to.

I'm going to remove the initialized Realm checks from directEval and nonEval

fixed in rev25 editor's draft


fixed in rev25 editor's draft