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

[Bug 20535] New: consider removing indexed property setters, creators and deleters

From: <bugzilla@jessica.w3.org>
Date: Mon, 31 Dec 2012 00:28:03 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20535-3890@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20535

            Bug ID: 20535
           Summary: consider removing indexed property setters, creators
                    and deleters
    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

Array-like interfaces defined using indexed property setters, creators and/or
deleters don't behave nicely.  They can't be used in conjunction with
Array.prototype functions unless we require the interface to support sparse
array indexes.  They also don't seem to be used (there are plenty of indexed
property getters on the other hand).

There is at least this use of an indexed property deleter:

http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-datatransferitemlist-interface

but that is pretty weird and bad design anyway IMO.


If we can remove indexed property setters, creators and deleters then we can
think about a solution for mutable array-like objects that work better with JS
Arrays.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 31 December 2012 00:28:05 UTC

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