Bug 6395 - Activation objects should not have __proto__ property
Summary: Activation objects should not have __proto__ property
Status: RESOLVED DUPLICATE of bug 6249
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Maciej Stachowiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-05 23:13 PST by Maciej Stachowiak
Modified: 2006-01-05 23:57 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Stachowiak 2006-01-05 23:13:16 PST
Activation objects (the objects that provide local scope for a function invocation) should not have a 
__proto__ property. They don't in Mozilla (which originated the __proto__ extension) and it allows various 
optimizations of property lookup if this is not supported.
Comment 1 Maciej Stachowiak 2006-01-05 23:20:40 PST
Here's a simple test:

javascript:alert((function() { __proto__.testVariable = 'found'; return window.testVariable; })())

This should show 'found' and does in Firefox 1.5 (but not in some older versions - presumably that means 
they decided to change this too from the way it was).
Comment 2 Maciej Stachowiak 2006-01-05 23:57:31 PST
This is also fixed by the changes for 6249.

*** This bug has been marked as a duplicate of 6249 ***