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
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:
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.cawrote:
Very cool Andrew. Does this affect the cross-origin policy? Many users
exploit the ability to
Specifically with iOS, setting the start page to a chrome-extension:// url
causes the underlying UIWebView to apply CORS policies to all XHR requests.
UIWebView seems to use the same restrictions as desktop Safari:
- Requests coming from file:/// urls do not use the Origin header
- Requests
Thanks for the details Ian.
In our experience, by-passing CORS policies is a HUGE bonus for most
developers. It would be rad if you can find a nice hackity-hack to get
around this so that we can also take advantage of WebSQL :)
Michael
On Wed, Apr 17, 2013 at 12:50 PM, Joe Bowser
On Wed, Apr 17, 2013 at 2:50 PM, Joe Bowser bows...@gmail.com wrote:
So, there isn't a CORS issue with Android?
I can neither confirm nor deny the existence of the alleged CORS issue on
Android :)
I'll probably know more about that tomorrow; I'll let you know what I find.
If we're using
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
