Re: CfC: move WebApps' test suites to Github; deadline March 22

2013-03-16 Thread Charles McCathie Nevile
On Fri, 15 Mar 2013 17:40:18 +0100, Arthur Barstow wrote: As you probably know, the HTMLWG recently moved its test suite to GitHub (GH). Tobie, Robin, Odin, Ms2ger and others propose WebApps do the same and this is a Call for Consensus to do so. We support the move. cheers Odin defined

Re: [webcomponents]: Making produce DocumentFragments

2013-03-16 Thread Dimitri Glazkov
On Thu, Mar 14, 2013 at 8:09 PM, Dominic Cooney wrote: > On Fri, Mar 15, 2013 at 9:43 AM, Dimitri Glazkov wrote: > >> Here's one scenario where keeping components Documents might be a good >> idea. Suppose you just built a multi-threaded parser into your renderer >> engine, and you would like to

Re: [webcomponents] linking using ?

2013-03-16 Thread Dimitri Glazkov
Hi Mike, the spec you're looking for is under development here: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/components/index.html :DG< On Fri, Mar 15, 2013 at 7:07 AM, Mike Kamermans wrote: > Hey all, > > I searched the archive at > http://lists.w3.org/Archives/Public/public-webapps

Re: [PointerLock] Should there be onpointerlockchange/onpointerlockerror properties defined in the spec

2013-03-16 Thread Anne van Kesteren
On Fri, Mar 15, 2013 at 6:57 PM, Vincent Scheib wrote: > I have added onipointerlockchange and onpointerlockerror to the partial > document IDL in the pointer lock specification. > > Webkit currently only defines these event handler attributes on document. > Unless a reason is raised to add them e

Re: Pointer lock updated with clarification of lock and focus requirements.

2013-03-16 Thread Glenn Maynard
On Fri, Mar 15, 2013 at 5:24 PM, Vincent Scheib wrote: > After discussion with Olli Pettay I have clarified portions of the pointer > lock specification. > > https://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html > https://dvcs.w3.org/hg/pointerlock/diff/6543d83c0b74/index.html > > When r

Re: [IndexedDB] Closing connection in a versionchange transaction

2013-03-16 Thread Jonas Sicking
On Fri, Nov 30, 2012 at 3:26 PM, Joshua Bell wrote: > A spec oddity that we noticed - if you explicitly close a connection during > an upgradeneeded handler (or elsewhere in the transaction), the transaction > should complete (not abort) yet the connection fails (error), upgrading the > database b

Re: [IndexedDB] Attributes with undefined vs. null

2013-03-16 Thread Jonas Sicking
On Wed, Nov 7, 2012 at 10:53 AM, Joshua Bell wrote: > Various atttributes in IndexedDB signal "no value" with |undefined|: > > IDBKeyRange.lowerBound (if not set) > IDBKeyRange.upperBound (if not set) > IDBRequest.result (on error, or on successful deleteDatabase/get with no > value/delete/clear)

Re: [IndexedDB] better way of deleting records

2013-03-16 Thread Jonas Sicking
On Tue, Jan 15, 2013 at 7:19 PM, Kyaw Tun wrote: > From developer point of view, IDBObjectStore.delete method cannot be used > directly in most use case, since IDBObjectStore.delete returns undefined. > IDBObjectStore.delete(random_key) always receives onsuccess event, but > nothing happen. Curren

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

2013-03-16 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681 Jonas Sicking changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

Re: IndexedDB, what were the issues? How do we stop it from happening again?

2013-03-16 Thread Jonas Sicking
On Wed, Mar 6, 2013 at 10:14 AM, Alec Flett wrote: > My primary takeaway from both working on IDB and working with IDB for some > demo apps is that IDB has just the right amount of complexity for really > large, robust database use.. but for a "welcome to noSQL in the browser" it > is way too comp

Re: IndexedDB, what were the issues? How do we stop it from happening again?

2013-03-16 Thread Jonas Sicking
On Wed, Mar 6, 2013 at 6:01 AM, Alex Russell wrote: > I've avoided weighing in on this thread until I had more IDB experience. > I've been wrestling with it on two fronts of late: > > A re-interpretation of the API based on Futures: > https://github.com/slightlyoff/DOMFuture/tree/master/reworked_A