Re: Inconsistency between IDBObjectStore.openCursor, IDBIndex.openCursor, and IDBIndex.openKeyCursor

2011-05-12 Thread Jonas Sicking
On Thursday, May 12, 2011, Israel Hilerio wrote: > Async API: > IDBObjectStore.openCursor stipulates that "The steps are run with this > IDBObjectStore as source ..." > IDBIndex.openCursor stipulates that "The steps are run with this IDBIndex as > source ..." > IDBIndex.openKeyCursor stipulates

Inconsistency between IDBObjectStore.openCursor, IDBIndex.openCursor, and IDBIndex.openKeyCursor

2011-05-12 Thread Israel Hilerio
Async API: IDBObjectStore.openCursor stipulates that "The steps are run with this IDBObjectStore as source ..." IDBIndex.openCursor stipulates that "The steps are run with this IDBIndex as source ..." IDBIndex.openKeyCursor stipulates that "The steps are run with this IDBObjectStore as source ..

Re: [widgets] WARP usability issue

2011-05-12 Thread timeless
2011/5/12 Scott Wilson : > I'd be tempted to just strip off any trailing slashes on import. > Actually I might do that for all path components in a WARP origin rather than > throw an error. So. I was hoping it could be fixed by Stores when they import, but of course the signature would be voided

Re: [widgets] WARP usability issue

2011-05-12 Thread Marcos Caceres
On Thu, May 12, 2011 at 2:43 PM, timeless wrote: > On Thu, May 12, 2011 at 2:50 PM, Marcos Caceres > wrote: >> did you just say "the tools will save us?" :) > > i did,  did! > >> It's better to avoid confusion >> altogether and make this a bit more liberal, me thinks. > > i think we risk people t

Re: [widgets] WARP usability issue

2011-05-12 Thread Scott Wilson
On 12 May 2011, at 13:43, timeless wrote: > On Thu, May 12, 2011 at 2:50 PM, Marcos Caceres > wrote: >> did you just say "the tools will save us?" :) > > i did, did! > >> It's better to avoid confusion >> altogether and make this a bit more liberal, me thinks. > > i think we risk people thin

Re: [widgets] WARP usability issue

2011-05-12 Thread timeless
On Thu, May 12, 2011 at 2:50 PM, Marcos Caceres wrote: > did you just say "the tools will save us?" :) i did, did! > It's better to avoid confusion > altogether and make this a bit more liberal, me thinks. i think we risk people thinking that paths are allowed and meaningful. i'd rather avoid

Re: [widgets] WARP usability issue

2011-05-12 Thread timeless
2011/5/12 Marcos Caceres : > The following rule is too restrictive in WARP: > > "If origin is not a valid IRI, *if it has components other than scheme > and iauthority*, if it has no host component, or if it has a iuser > info component, then this element is in error and the user agent must > ignor

Re: [widgets] WARP usability issue

2011-05-12 Thread Marcos Caceres
On Thu, May 12, 2011 at 1:50 PM, Marcos Caceres wrote: > On 5/12/11 1:38 PM, timeless wrote: >> >> 2011/5/12 Marcos Caceres: >>> >>> The following rule is too restrictive in WARP: >>> >>> "If origin is not a valid IRI, *if it has components other than scheme >>> and iauthority*, if it has no host

Re: [widgets] WARP usability issue

2011-05-12 Thread Marcos Caceres
On 5/12/11 1:38 PM, timeless wrote: 2011/5/12 Marcos Caceres: The following rule is too restrictive in WARP: "If origin is not a valid IRI, *if it has components other than scheme and iauthority*, if it has no host component, or if it has a iuser info component, then this element is in error an

Re: [widgets] WARP usability issue

2011-05-12 Thread Marcos Caceres
On 5/12/11 12:41 PM, Charles McCathieNevile wrote: On Thu, 12 May 2011 12:27:33 +0200, Marcos Caceres wrote: Hi, The following rule is too restrictive in WARP: "If origin is not a valid IRI, *if it has components other than scheme and iauthority*, if it has no host component, or if it has a

Re: [widgets] WARP usability issue

2011-05-12 Thread Charles McCathieNevile
On Thu, 12 May 2011 12:27:33 +0200, Marcos Caceres wrote: Hi, The following rule is too restrictive in WARP: "If origin is not a valid IRI, *if it has components other than scheme and iauthority*, if it has no host component, or if it has a iuser info component, then this element is in erro

[widgets] WARP usability issue

2011-05-12 Thread Marcos Caceres
Hi, The following rule is too restrictive in WARP: "If origin is not a valid IRI, *if it has components other than scheme and iauthority*, if it has no host component, or if it has a iuser info component, then this element is in error and the user agent must ignore this element." For the "if it

Re: Overview of W3C technologies for mobile Web applications

2011-05-12 Thread Michael[tm] Smith
Dominique Hazael-Massieux , 2011-05-12 10:41 +0200: > Since I've received at least one offer to help keeping the page up to > date if moved to a wiki, I've moved a copy of the document above to the > wiki page at > http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile > > In the upcomin

Re: Overview of W3C technologies for mobile Web applications

2011-05-12 Thread Dominique Hazael-Massieux
Le jeudi 24 février 2011 à 16:03 +0100, Dominique Hazael-Massieux a écrit : > As part of a European research project I'm involved in [1], I've > compiled a report on the existing technologies in development (or in > discussion) at W3C for building Web applications and that are > particularly releva

Re: [File API: FileSystem] Path restrictions and case-sensitivity

2011-05-12 Thread timeless
On Thu, May 12, 2011 at 3:02 AM, Eric U wrote: > There are a few things going on here: yes > 1) Does the filesystem preserve case?  If it's case-sensitive, then > yes.  If it's case-insensitive, then maybe. > 2) Is it case-sensitive?  If not, you have to decide how to do case > folding, and that