Quota Management API error codes

2012-07-03 Thread Jochen Eisinger
Hey, while reading http://www.w3.org/TR/quota-api/#quota-handling-in-storage-apiI wondered what the desired behavior was when the UA refuses to grant any quota? I think it would be nice to specify this in the standard. E.g. currently WebKit will throw a QuotaExceeded exception when a page tries t

Quota Management API error codes

2012-07-03 Thread Kinuko Yasuda
(Replying to a message I got separately) Thanks for the feedback! Hmm if a write fails because the UA does not grant any quota for the site I think it must throw a QuotaExceeded exception, so that website authors or the users could tell how they can re-enable writing to the storage (e.g. by allow

[Bug 17685] New: Hello, Please make the standard web socket api include a spec for an in browser "listener" socket. Meaning: a javascript application is able to create a server listener socket in th

2012-07-03 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17685 Summary: Hello, Please make the standard web socket api include a spec for an in browser "listener" socket. Meaning: a javascript application is able to create a server liste

[Bug 17681] New: [IndexedDB] Operations that raise multiple exceptions types should define order

2012-07-03 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681 Summary: [IndexedDB] Operations that raise multiple exceptions types should define order Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Sta

RE: RfC: LCWD of Indexed Database; deadline June 21

2012-07-03 Thread Eliot Graff
Apologies for not responding sooner. I've been swamped on a couple of projects. I'm happy to do the lion's share of the clerical work for going through the comments and tracking them. I created a tracking sheet [1] when I put together the LCWD and will add items to that. Israel and I will meet l

[selectors-api] New Implementation Report for Updated Testsuite

2012-07-03 Thread Lachlan Hunt
I have now generated a new implementation report [1] to go with the updated testsuite. As I detailed previously on public-webapps-testsuite [2], the new tests use testharness.js and, as a result, some of the tests which passed under the old framework now fail in some browsers. This is mostly

[Bug 17675] New: Parameters to slice

2012-07-03 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17675 Summary: Parameters to slice Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Fi