[html5] r2811 - [giow] (2) 'this' in the global scope in JS shouldn't return the window object, [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Feb 12 19:16:30 PST 2009
Author: ianh
Date: 2009-02-12 19:16:29 -0800 (Thu, 12 Feb 2009)
New Revision: 2811
Modified:
index
source
Log:
[giow] (2) 'this' in the global scope in JS shouldn't return the window object, it should return the proxy. Hopefully one day this'll move to the ES specs.
Modified: index
===================================================================
--- index 2009-02-13 03:12:15 UTC (rev 2810)
+++ index 2009-02-13 03:16:29 UTC (rev 2811)
@@ -37677,6 +37677,11 @@
empty object, it can't do anything that interacts with the
environment.</p>
+ <p>If the <a href="#script's-global-object">script's global object</a> is a
+ <code><a href=#window>Window</a></code> object, then in JavaScript, the <code title="">this</code> keyword in the global scope must, contrary to
+ the ECMAScript specification, return the <code><a href=#window>Window</a></code>
+ object's <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+
</dd>
<dt>A relationship with the <dfn id="script's-browsing-context">script's browsing context</dfn></dt>
Modified: source
===================================================================
--- source 2009-02-13 03:12:15 UTC (rev 2810)
+++ source 2009-02-13 03:16:29 UTC (rev 2811)
@@ -40213,6 +40213,12 @@
empty object, it can't do anything that interacts with the
environment.</p>
+ <p>If the <span>script's global object</span> is a
+ <code>Window</code> object, then in JavaScript, the <code
+ title="">this</code> keyword in the global scope must, contrary to
+ the ECMAScript specification, return the <code>Window</code>
+ object's <code>WindowProxy</code> object.</p>
+
</dd>
<dt>A relationship with the <dfn>script's browsing context</dfn></dt>
More information about the Commit-Watchers
mailing list