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

[Bug 21929] New: named properties object should disallow definition of non-configurable properties

From: <bugzilla@jessica.w3.org>
Date: Sun, 05 May 2013 02:31:07 +0000
To: public-script-coord@w3.org
Message-ID: <bug-21929-3890@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21929

            Bug ID: 21929
           Summary: named properties object should disallow definition of
                    non-configurable properties
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
          Assignee: cam@mcc.id.au
          Reporter: cam@mcc.id.au
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-script-coord@w3.org

The named properties object exposes named properties as configurable data
properties.  There is no special [[DefineOwnProperty]], so we can still define
our own on the object.  [[DefineOwnProperty]] can successfully set an own
property on the object, although named properties will still shadow them when
you get them.  This allows [[DefineOwnProperty]] to set a non-configurable
property, which then can be exposed as configurable if a named property starts
existing with the same name later.  This breaks an invariant on
[[Configurable]].  We could have [[DefineOwnProperty]] force [[Configurable]] =
true, just like [[DefineOwnProperty]] for platform objects implementing
interfaces that support named properties.  Or we could disallow expandos on the
named properties object.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Sunday, 5 May 2013 02:31:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:49 UTC