Re: Mutation Observers: a replacement for DOM Mutation Events

2011-10-12 Thread Sean Hogan
On 12/10/11 3:26 AM, Tab Atkins Jr. wrote: On Mon, Oct 10, 2011 at 7:51 PM, Sean Hoganshogu...@westnet.com.au wrote: On 24/09/11 7:16 AM, Adam Klein wrote: - Is free of the faults of the existing Mutation Events mechanism (enumerated in detail here:

Re: Mutation Observers: a replacement for DOM Mutation Events

2011-10-12 Thread Olli Pettay
On 10/12/2011 02:00 PM, Sean Hogan wrote: On 12/10/11 3:26 AM, Tab Atkins Jr. wrote: On Mon, Oct 10, 2011 at 7:51 PM, Sean Hoganshogu...@westnet.com.au wrote: On 24/09/11 7:16 AM, Adam Klein wrote: - Is free of the faults of the existing Mutation Events mechanism (enumerated in detail here:

Re: Mutation Observers: a replacement for DOM Mutation Events

2011-10-12 Thread Rafael Weinstein
Hi Sean, I find it hard to reason about cases in the abstract. None of the examples you list seem concerning to me (i.e. I believe they can be properly handled), but perhaps it's a failure of my imagination. Maybe you can provide concrete examples (i.e. with code snippets, actual instances of

[IndexedDB] IDBObjectStore.delete should accept a KeyRange

2011-10-12 Thread Jonas Sicking
Currently IDBObjectStore.count/get/openCursor and IDBIndex.count/get/openCursor/openKeyCursor all take a key or a KeyRange. However IDBObjectStore.delete only accepts keys. We should fix this to allow .delete to accept a KeyRange as well. / Jonas

[Bug 14441] New: Note in IDBIndex.getKey is incorrect

2011-10-12 Thread bugzilla
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14441 Summary: Note in IDBIndex.getKey is incorrect Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2

[indexeddb] Calling IDBDatabase.close inside onupgradeneeded handler

2011-10-12 Thread Israel Hilerio
If a db connection is closed inside the onupgradeneeded handler, section 4.1 step #8 states that we should return an ABORT_ERR and abort steps. This implies that the transaction should fail. Since today, the db is closed after all requests have been processed, we don't see the reason why we

Re: [indexeddb] Calling IDBDatabase.close inside onupgradeneeded handler

2011-10-12 Thread Jonas Sicking
On Wed, Oct 12, 2011 at 4:06 PM, Israel Hilerio isra...@microsoft.com wrote: If a db connection is closed inside the onupgradeneeded handler, section 4.1 step #8 states that we should return an ABORT_ERR and abort steps. This implies that the transaction should fail. Since today, the db is

RE: [indexeddb] Calling IDBDatabase.close inside onupgradeneeded handler

2011-10-12 Thread Israel Hilerio
On Wednesday, October 12, 2011 4:21 PM, Jonas Sicking wrote: On Wed, Oct 12, 2011 at 4:06 PM, Israel Hilerio isra...@microsoft.com wrote: If a db connection is closed inside the onupgradeneeded handler, section 4.1 step #8 states that we should return an ABORT_ERR and abort steps. This

[DOM3Events] Oustanding issues (was: [DOM3Events] CR)

2011-10-12 Thread Jacob Rossi
Hi Anne, Talking with Doug this morning, it seems he didn't have a chance to reply to your mail below since he's been pretty busy. I've provided responses below inline, sorry for the delay! Thanks, Jacob -Original Message- From: Anne van Kesteren [mailto:ann...@opera.com] Sent:

re: [DOM3 Events] Some comments on Basic Event Interfaces

2011-10-12 Thread Jacob Rossi
Ms2ger, Thanks for all your suggestions on DOM3Events. There's some good grammatical fix ups that you suggest. These shouldn't affect implementers, but Doug and I can integrate these suggestions to improve the readability. As for the functional comments: 4.3 Interface EventTarget

Re: [DOM3Events] Oustanding issues (was: [DOM3Events] CR)

2011-10-12 Thread Anne van Kesteren
On Thu, 13 Oct 2011 09:54:26 +0900, Jacob Rossi jacob.ro...@microsoft.com wrote: Talking with Doug this morning, it seems he didn't have a chance to reply to your mail below since he's been pretty busy. I've provided responses below inline, sorry for the delay! Thanks for getting to them.

RE: [DOM3Events] Oustanding issues (was: [DOM3Events] CR)

2011-10-12 Thread Jacob Rossi
-Original Message- From: Anne van Kesteren [mailto:ann...@opera.com] Sent: Wednesday, October 12, 2011 6:27 PM To: Doug Schepers; Jacob Rossi Cc: public-webapps; Adrian Bateman; Arthur Barstow; Chaals McCathieNevile; www-...@w3.org Subject: Re: [DOM3Events] Oustanding issues (was:

Re: Mutation Observers: a replacement for DOM Mutation Events

2011-10-12 Thread Sean Hogan
On 13/10/11 12:34 AM, Olli Pettay wrote: On 10/12/2011 02:00 PM, Sean Hogan wrote: On 12/10/11 3:26 AM, Tab Atkins Jr. wrote: On Mon, Oct 10, 2011 at 7:51 PM, Sean Hoganshogu...@westnet.com.au wrote: On 24/09/11 7:16 AM, Adam Klein wrote: - Is free of the faults of the existing Mutation

Re: Mutation Observers: a replacement for DOM Mutation Events

2011-10-12 Thread Sean Hogan
On 13/10/11 4:50 AM, Rafael Weinstein wrote: Hi Sean, I find it hard to reason about cases in the abstract. None of the examples you list seem concerning to me (i.e. I believe they can be properly handled), but perhaps it's a failure of my imagination. I didn't say they can't be properly

Re: Mutation Observers: a replacement for DOM Mutation Events

2011-10-12 Thread Ryosuke Niwa
On Wed, Oct 12, 2011 at 8:14 PM, Sean Hogan shogu...@westnet.com.au wrote: Maybe you can provide concrete examples (i.e. with code snippets, actual instances of use cases, etc...) Actually, it is the proponents of changing the status-quo and of the more complex solution who bear more

Re: [DOM3Events] Oustanding issues (was: [DOM3Events] CR)

2011-10-12 Thread Anne van Kesteren
On Thu, 13 Oct 2011 11:32:34 +0900, Jacob Rossi jacob.ro...@microsoft.com wrote: Your welcome, I appreciate your tolerance! I made a sweep in good faith through the list archives and was unable to find other unanswered issues. It is somewhat sad comments are not being tracked. I just went