Ian has been running into some issues with CORS while working on porting an
app, I'll let him comment on specifics.


On Wed, Apr 17, 2013 at 12:27 PM, Michael Brooks
<mich...@michaelbrooks.ca>wrote:

> Very cool Andrew. Does this affect the cross-origin policy? Many users
> exploit the ability to make requests across multiple domains.
>
> Michael
>
>
> On Wed, Apr 17, 2013 at 8:35 AM, Andrew Grieve <agri...@chromium.org>
> wrote:
>
> > Just tried it with:
> >
> > chrome-extension://asdf/chromeapp.html?foo:1?#asdf?ds#af:s
> >
> > Had to make a slight tweak to IceCreamCordovaWebViewClient, but it worked
> > fine.
> >
> >
> > On Wed, Apr 17, 2013 at 12:39 AM, Joe Bowser <bows...@gmail.com> wrote:
> >
> > > How does this affect URI handling?  We've had far bigger issues with
> > > file:///android-asset failing on ICS+.  Did you test with URIs that
> > contain
> > > a question mark, pound or a colon?
> > >
> > > On Apr 16, 2013 7:23 PM, "Andrew Grieve" <agri...@chromium.org> wrote:
> > >
> > >> Found a juicy hack that works around the webview disabling WebSQL for
> > >> file: URLs.
> > >>
> > >> For our Chrome Apps plugins, we serve apps from chrome-extension://
> URLs
> > >> instead of file:// URLs. This is possible via
> shouldInterceptRequest(),
> > >> where we just map the requests to the files.
> > >>
> > >> So... I had the idea to test the WebSQL mobile-spec tests under this
> > >> scheme (while disabling Android's custom WebSQL work-around), and it
> > seemed
> > >> to work fine.
> > >>
> > >> I think that this means that we could change Cordova app urls to be
> > >> cordova:// (for ICS+), and could then delete the storage plugin.
> > >>
> > >> What do you think?
> > >>
> > >
> >
>

Reply via email to