W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2011

[Bug 14746] New: Clarify what happens when you try using unsupported property indexes

From: <bugzilla@jessica.w3.org>
Date: Wed, 09 Nov 2011 20:11:19 +0000
To: public-script-coord@w3.org
Message-ID: <bug-14746-3890@http.www.w3.org/Bugs/Public/>

           Summary: Clarify what happens when you try using unsupported
                    property indexes
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
        AssignedTo: cam@mcc.id.au
        ReportedBy: ayg@aryeh.name
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-script-coord@w3.org says:

The following requirements apply to the definitions of indexed property
getters, setters, creators and deleters:

* If an indexed property getter was specified using an operation with an
identifier, then the value returned when indexing the object with a given index
is the value that would be returned by invoking the operation, passing the
index as its only argument.

By itself, this makes it look like this is true for *any* index.  I was
confused and thought this is what was actually intended (see bug 14743). 
However, 4.7.2 defines that if the index is not a supported property index,
nothing special happens, and regular ES behavior takes hold.

Perhaps "when indexing the object with a given index" should be changed to
"when indexing the object with a given supported property index" or something? 
Are there other places where similar changes are needed?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 9 November 2011 20:11:28 UTC

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