es-lab
es-lab copied to clipboard
tvcutsem
Automatically exported from code.google.com/p/es-lab
## Historical mistake We made a mistake in the Proxy design (@tvcutsem agrees): The proxy does a `[[Get]]` on the handler's trap properties each time it wants to trap. Rather,...
``` In this patch: * I define LeakyWeakMaps (implemented with a key/value arrays pair) * I replace the 2 key/values array pairs (hidden record and leaky weakmap for non-extensible objects)...
``` Bug : http://jsfiddle.net/jkegJ/2/ Related github issue : https://github.com/nrstott/traits.js/pull/1 It would appear that getter/setter's on Object.prototype are broken when using `map[name] = pd` at http://code.google.com/p/es-lab/source/browse/trunk/src/traits/traits.js#272 Replacing it with a `defineProperty`...
``` On major browsers (tested on FF5, Chrome 11 and Opera 11.11), window.frames === window. This could be a way for a script writer to access the global object without...
``` in line 82 of traits.js : http://code.google.com/p/es-lab/source/browse/trunk/src/traits/traits.js#82 it seems the getPrototypeOf fallback implementation is wrong and should really be: return obj.prototype; instead of return Object.prototype; Since I didn't try...
``` a small correction ``` Original issue reported on code.google.com by `[email protected]` on 4 May 2011 at 1:02 Attachments: - [forwardingHandler.js.patch](https://storage.googleapis.com/google-code-attachments/es-lab/issue-15/comment-0/forwardingHandler.js.patch)
``` Try typing it into http://es-lab.googlecode.com/svn/trunk/site/esparser/index.html See https://bugs.ecmascript.org/show_bug.cgi?id=8 ``` Original issue reported on code.google.com by `[email protected]` on 9 Feb 2011 at 1:40
``` What steps will reproduce the problem? 1. Load the page 2. Open the source 3. There's no doctype before What is the expected output? What do you see instead?...
``` Parser does not catch all 'early errors' yet (cf. Section 16 of the ES5 spec) Intent is to write a post-processing tree-walker that reports these. ``` Original issue reported...
``` Future reserved keywords for strict-mode not yet supported by the parser (cf. ES5 spec Section 7.6.1.2). ``` Original issue reported on code.google.com by `[email protected]` on 19 Dec 2009 at...