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

[Bug 20394] New: [IndexedDB] Spec should use WebIDL concepts such as sequence<T> rather than Array

From: <bugzilla@jessica.w3.org>
Date: Fri, 14 Dec 2012 18:59:51 +0000
To: public-webapps@w3.org
Message-ID: <bug-20394-2927@http.www.w3.org/Bugs/Public/>

            Bug ID: 20394
           Summary: [IndexedDB] Spec should use WebIDL concepts such as
                    sequence<T> rather than Array
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
          Assignee: dave.null@w3.org
          Reporter: jsbell@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

In various places in the spec such as the interpretation of key path values,
the spec explicitly defines special input for ECMAScript Arrays. Most of the
rest of the platform defines this via WebIDL's ECMAScript binding which is
closer to "duck typing" rather than "is-a". For example, an operation that
accepts sequence<DOMString> would be satisfied by this input:

{ 'length': 2, '0': 'first', '1': 'second' }

... even though it is not an ECMAScript array.

This applies most easily to Key Paths, which are defined to be DOMStrings or
Arrays of DOMStrings.


Both Chrome and Firefox do "is-a" checks here, but changing this wouldn't break
anything. I don't think we need to do this for the v1 edition of the spec, but
adhering more closely to WebIDL for v2 would be nice.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 14 December 2012 18:59:53 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:50 UTC