Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of lorin.beer.dev@gmail.com
 designates 209.85.223.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CD7729E9.1B6CA%fil@adobe.com>
References: 
 <CAASJe79OPhQ+7N14SGrpHXh1n8a6vC6TRAp=O=E0pg9Psnoz6A@mail.gmail.com>
	<CD7729E9.1B6CA%fil@adobe.com>
Date: Tue, 26 Mar 2013 10:39:53 -0700
Message-ID: 
 <CAASJe78cXN_i68L1aTcQUZkP1E__QNguB8Fts-ugmwLkndQskg@mail.gmail.com>
Subject: Re: Mobile Spec File Tests Query string
From: Lorin Beer <lorin.beer.dev@gmail.com>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=e89a8f646d15b6997c04d8d76818

--e89a8f646d15b6997c04d8d76818
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

just went over this briefly with Brian, resolveLocalFileSystemURI is our
desired inclusion to or form of the w3 spec due to our use case being
outside the browser sandbox.

So we just make sure URI conforms to URL?

in which case, original question: is there any semantic reason for a query
tag at the end of a file resource identifier? Or are we just making sure it
can handle the breadth of the URL/URI syntax gracefully?


On Tue, Mar 26, 2013 at 10:33 AM, Filip Maj <fil@adobe.com> wrote:

> O that=B9s the one!
>
> On 3/26/13 10:29 AM, "Lorin Beer" <lorin.beer.dev@gmail.com> wrote:
>
> >yeah, couldn't track that down either? Anyone? Paging
> >"resolveLocalFileSystemURI" spec?
> >
> >the W3 spec has resolveLocalFileSystemURL only
> ><
> http://www.w3.org/TR/file-system-api/#widl-LocalFileSystem-resolveLocalFi
> >leSystemURL-void-DOMString-url-EntryCallback-successCallback-ErrorCallba=
ck
> >-errorCallback>
> >
> >
> >On Tue, Mar 26, 2013 at 10:23 AM, Filip Maj <fil@adobe.com> wrote:
> >
> >> I'm pretty sure the test simply follows the spec.. Which I can't find
> >> (where the f is resolvelocalfilesystemuri spec'ed?)
> >>
> >> On 3/26/13 10:18 AM, "Lorin Beer" <lorin.beer.dev@gmail.com> wrote:
> >>
> >> >Hey guys,
> >> >
> >> >In file.tests.js, line 267:
> >> >
> >>
> >>
> https://github.com/apache/cordova-mobile-spec/blob/master/autotest/tests/
> >>f
> >> >ile.tests.js#L267
> >> >
> >> >there is a URI passed to resolveLocalFileSystemURI with a query strin=
g
> >> >appended to the end. The test is meant to return a valid entry.
> >> >
> >> >BB7 and BB10 currently flunk the test, returning with an "Invalid
> >>Symbol"
> >> >type error.
> >> >
> >> >I checked the iOS handling of this:
> >> >
> >>
> >>
> https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVF
> >>i
> >> >le.m#L218
> >> >
> >> >and the query string is stripped out with the call to NSUrl path.
> >> >
> >> >Questions:
> >> >
> >> >1. what's the point of the test? Just to test handling of valid URI
> >> >with syntactically but semantically meaningless query string?
> >> >2. is there any purpose to a query string on a URI mean to be resolve=
d
> >>to
> >> >a
> >> >file path?
> >> >
> >> >Just want to understand this fully before implementing the handling o=
n
> >>BB
> >>
> >>
>
>

--e89a8f646d15b6997c04d8d76818--