W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2013

[Bug 20777] Getting a property from the global scope polluter ends up in an infinite loop

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Jan 2013 17:05:44 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20777-3890-EzjVU3qPRs@http.www.w3.org/Bugs/Public/>

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> ---
Note that we only need to pass in the Window because we need to know stuff
about its interface.  We could pass the interface to the named property
visibility algorithm and then pass in the gsp or its proto...

That said, I'm also not sure what step 4 of this algorithm means.  Does it not
involve calling [[GetOwnProperty]] on the object?  Should it talk about calling
the default [[GetOwnProperty]] or something?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 25 January 2013 17:05:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:08 UTC