On Tue, Jun 14, 2011 at 9:00 AM, Israel Hilerio wrote:
> The description for the IDBIndex.getKey tells us to use “the steps for
>
> retrieving a value from an index" as the operation. These steps seem to
> deal
>
> with how to retrieve values and not keys. It seems, we need a new section
>
> sim
On Fri, 15 Apr 2011, Ian Clelland wrote:
>
> Section 4:
> When close() is called on the EventSource object, the initial connection may
> not have been established yet, or a reconnection could be scheduled for some
> arbitrary time in the future (not currently being attempted).
Fixed.
> > Only if
The correct URL is:
http://www.w3.org/TR/2011/WD-contacts-api-20110616/
On Jun/15/2011 1:47 PM, Arthur Barstow wrote:
On June 16, the Device API group will publish a Last Call Working
Draft of its Calendar API spec:
http://www.w3.org/TR/2010/WD-contacts-api-20110616/
Individuals
On Thursday, June 16, 2011 4:49 PM, Jonas Sicking wrote:
> On Wed, Jun 15, 2011 at 5:34 PM, Israel Hilerio
> wrote:
> > On Wednesday, June 15, 2011 3:27 PM, Jonas Sicking wrote:
> >> On Wed, Jun 15, 2011 at 2:15 PM, Israel Hilerio
> >>
> >> wrote:
> >> > IDBFactory.deleteDatabase can be called wi
On Thursday, June 16, 2011 3:09 PM, Cameron McCormack wrote:
> Israel Hilerio:
> > Great! I will work with Eliot to update the spec for the two APIs
> > below, including their Synchronous counterparts, with:
> > ---
> > dictionary IDBDatabaseOptionalParameters {
> >DOMString keyPath = null
On Wed, Jun 15, 2011 at 5:34 PM, Israel Hilerio wrote:
> On Wednesday, June 15, 2011 3:27 PM, Jonas Sicking wrote:
>> On Wed, Jun 15, 2011 at 2:15 PM, Israel Hilerio
>> wrote:
>> > IDBFactory.deleteDatabase can be called without ever invoking the
>> > IDBDatabase.setVersion and requires a VERSION
Israel Hilerio:
> Great! I will work with Eliot to update the spec for the two APIs
> below, including their Synchronous counterparts, with:
> ---
> dictionary IDBDatabaseOptionalParameters {
>DOMString keyPath = null;
That would need to be
DOMString? keyPath = null;
(or else just wri
On Monday, June 13, 2011 1:17 PM, Jonas Sicking wrote:
> On Mon, Jun 13, 2011 at 1:00 PM, Israel Hilerio
> wrote:
> > On Tuesday, June 07, 2011 4:53 PM, Cameron McCormack wrote:>
> timeless:
> >> > would having a field: "mandatory" which indicates which arguments
> >> > (or feature names) must be
On Thu, 2011-06-16 at 11:59 -0700, James Robinson wrote:
> That text requires the storage mutex, which has not and will not be
> implemented by any vendors, let alone 2 interoperable implementations,
> so it seems rather doomed.
Where does it do that? My only intent was to fix 12111 and nothing
el
That text requires the storage mutex, which has not and will not be
implemented by any vendors, let alone 2 interoperable implementations, so it
seems rather doomed.
- James
On Jun 16, 2011 8:58 AM, "Philippe Le Hegaret" wrote:
> Art wrote:
>> All - given that addressing 12111 is a low priority f
On Wed, Jun 15, 2011 at 11:32 PM, timeless wrote:
> Some computers live behind proxies which do not provide for client
> based dns lookups. instead a client tells the proxy "i would like to
> talk to " or "i would like to get " and the proxy says
> "here's a connection for " or "here's the data fo
Art wrote:
> All - given that addressing 12111 is a low priority for Ian, one way
> forward is for someone else to create a concrete proposal.
Here is a concrete proposal:
http://www.w3.org/2011/06/Web%20Storage.html
Philippe
On Thu, Jun 16, 2011 at 12:23 PM, Marcos Caceres
wrote:
> On Wed, Jun 15, 2011 at 7:47 PM, Arthur Barstow wrote:
>> On June 16, the Device API group will publish a Last Call Working Draft of
>> its Calendar API spec:
>
>> http://www.w3.org/TR/2010/WD-contacts-api-2
On Wed, Jun 15, 2011 at 7:47 PM, Arthur Barstow wrote:
> On June 16, the Device API group will publish a Last Call Working Draft of
> its Calendar API spec:
> http://www.w3.org/TR/2010/WD-contacts-api-20110616/
Link should be:
http://www.w3.org/TR/2010/WD-contacts-api
14 matches
Mail list logo
