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

[Bug 20777] New: 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:00:55 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20777-3890@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20777

            Bug ID: 20777
           Summary: Getting a property from the global scope polluter ends
                    up in an infinite loop
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
          Assignee: cam@mcc.id.au
          Reporter: Ms2ger@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: bzbarsky@mit.edu, mike@w3.org,
                    public-script-coord@w3.org

Calling [[GetOwnProperty]] on the GSP ends us in [1]. In step 3, we call the
"named property visibility algorithm" [2] with object /object/ (==window). In
step 7 there, we call [[HasProperty]] on window.__proto__ == Window.prototype.
This walks the prototype chain [3] and ends up calling [[GetOwnProperty]] on
the GSP again.

[1]
http://dev.w3.org/2006/webapi/WebIDL/#named-properties-object-getownproperty
[2] http://dev.w3.org/2006/webapi/WebIDL/#dfn-named-property-visibility
[3] http://ecma-international.org/ecma-262/5.1/#sec-8.12.6

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

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:08 UTC