- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Dec 2010 11:19:23 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11567
Summary: IndexedDB should utilize the new WebIDL static feature
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Indexed Database API
AssignedTo: dave.null@w3.org
ReportedBy: jorlow@chromium.org
QAContact: member-webapi-cvs@w3.org
CC: mike@w3.org, public-webapps@w3.org
Per Jonas:
To construct a key range a set of constructors are available. In
languages with interface objects [WEBIDL], these constructors are
available on the IDBKeyRange interface object. In other languages
these constructors are available through language specific means, for
example as static functions"
But I see that I forgot to say that the IDBKeyRangeConstructors
interface implements these constructors.
However WebIDL nowadays have support for "static" so there is no
longer a need for a separate interface. We should just do
interface IDBKeyRange {
readonly attribute any lower;
readonly attribute any upper;
readonly attribute boolean lowerOpen;
readonly attribute boolean upperOpen;
static IDBKeyRange only (in any value);
static IDBKeyRange lowerBound (in any bound, in optional boolean open);
static IDBKeyRange upperBound (in any bound, in optional boolean open);
static IDBKeyRange bound (in any lower, in any upper,
in optional boolean lowerOpen,
in optional boolean upperOpen);
};
--
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 Friday, 17 December 2010 11:19:26 UTC