Battery Status API vs. Geolocation API

2011-06-06 Thread Andres Riofrio
Hello, I have some comments on the Battery Status API. I was wondering why it was that the battery status API is exposed using Events (and adding an additional requirement When an event listener is registered with the event type batterystatus, then the User Agent must dispatch a

Re: Battery Status API vs. Geolocation API

2011-06-06 Thread Dominique Hazael-Massieux
Hello Andres, The Battery Status API is deliverable of the Device APIs Working Group, so I'm copying the group's list public-device-a...@w3.org. (keeping public-webapps in BCC FYI) Dom Le dimanche 05 juin 2011 à 22:44 -0700, Andres Riofrio a écrit : I have some comments on the Battery Status

Re: Battery Status API vs. Geolocation API

2011-06-06 Thread Arthur Barstow
[ Bcc public-webapps; please reply to public-device-a...@w3.org ] As noted in the Battery Status Event spec, comments for the spec should be sent to the DAP WG's mail list: public-device-a...@w3.org mailto:public-device-a...@w3.org On Jun/6/2011 1:44 AM, ext Andres Riofrio wrote: Hello, I

Re: Status of URL Interface?

2011-06-06 Thread Arthur Barstow
Given the positive support indicated, one way forward with respect to WebApps is for Adam to put his spec into WebApps' Mercurial repo and to continue related discussions on public-webapps. Note, WebApps cannot publish this spec (in w3.org/TR/) until the spec is included in the WG's charter.

Publishing an update of File API spec

2011-06-06 Thread Arthur Barstow
Hi Arun, Jonas, All, The last publication of the File API spec [ED] was last October so it would be good to publish a new Working Draft in w3.org/TR/. Since Tracker shows 0 bugs for the spec [Tracker] and the ED does not appear to identify any open issues, does the spec meet the Last Call

Re: Publishing an update of File API spec

2011-06-06 Thread Dominique Hazael-Massieux
Le lundi 06 juin 2011 à 08:55 -0400, Arthur Barstow a écrit : The last publication of the File API spec [ED] was last October so it would be good to publish a new Working Draft in w3.org/TR/. Since Tracker shows 0 bugs for the spec [Tracker] and the ED does not appear to identify any open

[indexeddb] Section 4.1 - Opening the database (error codes)

2011-06-06 Thread Israel Hilerio
The first step in section 4.1 Opening the database stipulates: 1. If these steps fail for any reason, return a error with the appropriate code and abort this algorithm. What are the expected error codes for IDBFactory.open? Israel

Re: [indexeddb] Section 4.1 - Opening the database (error codes)

2011-06-06 Thread Jonas Sicking
On Mon, Jun 6, 2011 at 9:29 AM, Israel Hilerio isra...@microsoft.com wrote: The first step in section 4.1 Opening the database stipulates: 1. If these steps fail for any reason, return a error with the appropriate code and abort this algorithm. What are the expected error codes for

RE: [indexeddb] Default direction of Cursors

2011-06-06 Thread Israel Hilerio
On Mon, May 23, 2011 at 4:30 PM, Jonas Sicking wrote: On Mon, May 23, 2011 at 12:54 PM, Israel Hilerio isra...@microsoft.com wrote: I noticed that we don't define the default direction of a cursor when accessing records.  Both, Firefox and Chrome go from smallest to largest.  This seems

Re: [indexeddb] Default direction of Cursors

2011-06-06 Thread Jonas Sicking
On Mon, Jun 6, 2011 at 9:47 AM, Israel Hilerio isra...@microsoft.com wrote: On Mon, May 23, 2011 at 4:30 PM, Jonas Sicking wrote: On Mon, May 23, 2011 at 12:54 PM, Israel Hilerio isra...@microsoft.com wrote: I noticed that we don't define the default direction of a cursor when accessing

RE: [indexeddb] Default direction of Cursors

2011-06-06 Thread Israel Hilerio
What about this: The default value for the range will be null which implies: IDBKeyRange.lower = undefined IDBKeyRange.upper = undefined IDBKeyRange.lowerOpen = false IDBKeyRange.upperOpen = false The default value for the direction will be IDBCursor.NEXT. Israel On Mon, Jun 6, 2011 at 10:03

Re: Request for feedback: DOMCrypt API proposal - random number generation

2011-06-06 Thread Aryeh Gregor
On Sat, Jun 4, 2011 at 1:52 AM, Yaron Sheffer yaronf.i...@gmail.com wrote: However, I would like to propose one additional feature: a cryptographically secure random number generator (CSRNG). This is a badly missed feature today. [And just as I'm posting, I now see that Rich Tibbett beat me to

[indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters

2011-06-06 Thread Israel Hilerio
Have you considered using the WebIDL dictionary definition as a mechanism to define the optional parameters in the IDBDatabase.createObjectStore method? Advantages at using the dictionary definition on WebIDL for optional parameters: . Provides a fixed, ordered set of key-value pairs . Removes

Re: [indexeddb] Section 4.1 - Opening the database (error codes)

2011-06-06 Thread Jeremy Orlow
Unknown err might make sense for implementation specific bugs/issues. (If it's not deeply tied to an implementation, it shouldn't be unknown though.) On Mon, Jun 6, 2011 at 9:43 AM, Jonas Sicking jo...@sicking.cc wrote: On Mon, Jun 6, 2011 at 9:29 AM, Israel Hilerio isra...@microsoft.com

WebApps-ISSUE-181 (FileError-Name): Use case for FileError and FileException name attribute [File API]

2011-06-06 Thread Web Applications Working Group Issue Tracker
WebApps-ISSUE-181 (FileError-Name): Use case for FileError and FileException name attribute [File API] http://www.w3.org/2008/webapps/track/issues/181 Raised by: Adrian Bateman On product: File API FileError [1] and FileException [2] both define a DOMString attribute called name that

WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API]

2011-06-06 Thread Web Applications Working Group Issue Tracker
WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API] http://www.w3.org/2008/webapps/track/issues/182 Raised by: Adrian Bateman On product: File API The File API adds an OperationNotAllowed exception

Re: [indexeddb] Default direction of Cursors

2011-06-06 Thread Jonas Sicking
On Mon, Jun 6, 2011 at 10:20 AM, Israel Hilerio isra...@microsoft.com wrote: What about this: The default value for the range will be null which implies: IDBKeyRange.lower = undefined IDBKeyRange.upper = undefined IDBKeyRange.lowerOpen = false IDBKeyRange.upperOpen = false Well, currently

Re: Request for feedback: DOMCrypt API proposal - random number generation

2011-06-06 Thread Yaron Sheffer
Sure, that would be much more efficient. And I agree with others on that thread that the API should be non-blocking, non-failing, i.e. akin to Linux /dev/urandom. But my more important point was the second API: allow the code to mix in any available entropy:

Re: [indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters

2011-06-06 Thread Jonas Sicking
On Mon, Jun 6, 2011 at 12:03 PM, Israel Hilerio isra...@microsoft.com wrote: Have you considered using the WebIDL dictionary definition as a mechanism to define the optional parameters in the IDBDatabase.createObjectStore method? Advantages at using the dictionary definition on WebIDL for

Re: Request for feedback: DOMCrypt API proposal - random number generation

2011-06-06 Thread James Robinson
On Mon, Jun 6, 2011 at 1:52 PM, Yaron Sheffer yaronf.i...@gmail.com wrote: ** Sure, that would be much more efficient. And I agree with others on that thread that the API should be non-blocking, non-failing, i.e. akin to Linux /dev/urandom. But my more important point was the second API:

[Bug 11113] [IndexedDB] The spec should be more explicit about the queuing of setVersion transactions

2011-06-06 Thread bugzilla
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3 Eliot Graff eliot...@microsoft.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED

Re: Request for feedback: DOMCrypt API proposal - random number generation

2011-06-06 Thread Yaron Sheffer
In a "real" browser, there should indeed be enough entropy, mostly from user actions. I don't know if this group cares about server-side uses, but if it does, servers have a real problem obtaining entropy. Especially in virtualized settings. Thanks, Yaron

Re: [indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters

2011-06-06 Thread Cameron McCormack
Jonas Sicking: The one outstanding issue that I know about is that we want IndexedDB to throw if any unknown parameters are specified. I don't know if WebIDL dictionaries support those yet. Or if it's something that we can specify in prose. I was waiting to see if anyone else had any views on

Re: [indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters

2011-06-06 Thread Jonas Sicking
On Mon, Jun 6, 2011 at 2:15 PM, Cameron McCormack c...@mcc.id.au wrote: Jonas Sicking: The one outstanding issue that I know about is that we want IndexedDB to throw if any unknown parameters are specified. I don't know if WebIDL dictionaries support those yet. Or if it's something that we

Re: [indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters

2011-06-06 Thread Cameron McCormack
Jonas Sicking: I don't know about other APIs. But it does seem very unfortunate to simply silently ignore unknown arguments to IDBDatabase.createObjectStore. Though then again, extra (and thus unknown) arguments are ignored to all other DOM calls. Right (not as defined in Web IDL at the

Re: WebApps-ISSUE-181 (FileError-Name): Use case for FileError and FileException name attribute [File API]

2011-06-06 Thread Aryeh Gregor
On Mon, Jun 6, 2011 at 4:28 PM, Web Applications Working Group Issue Tracker sysbot+trac...@w3.org wrote: FileError [1] and FileException [2] both define a DOMString attribute called name that contains the name of the error/exception constant as a string. Since this is not a useful human

[File API: FileSystem] Removed mimeType from toURL

2011-06-06 Thread Eric U
The optional mimeType parameter to Entry[Sync].toURL is redundant with url.createObjectURL. It also doesn't work with the URL format proposed in the notes and now implemented in Chromium. I have removed it from the spec. Eric

RE: [Indexeddb} Bug # 9653 - nullable violations on parameters

2011-06-06 Thread Israel Hilerio
On Tue, Apr 26, 2011 at 10:05 PM, Jonas Sicking wrote: On Tue, Apr 26, 2011 at 8:23 PM, Cameron McCormack c...@mcc.id.au wrote: Jonas Sicking: However it appears that that extended attribute is not present in newer versions of the WebIDL spec. Cameron, is this something that is planned

[indexeddb] IDBDatabase.setVersion non-nullable parameter has a default for null

2011-06-06 Thread Israel Hilerio
The parameter of IDBDatabase.setVersion is defined in the WebIDL as [TreatNullAs=EmptyString] but in the method definition it says that the parameter cannot be nullable. Do we want to enable null values? Israel

Re: [Indexeddb} Bug # 9653 - nullable violations on parameters

2011-06-06 Thread Jonas Sicking
On Mon, Jun 6, 2011 at 7:19 PM, Israel Hilerio isra...@microsoft.com wrote: On Tue, Apr 26, 2011 at 10:05 PM, Jonas Sicking wrote: On Tue, Apr 26, 2011 at 8:23 PM, Cameron McCormack c...@mcc.id.au wrote: Jonas Sicking: However it appears that that extended attribute is not present in