Hey How does this work with the fixes for the # that are present in Android 4.0 and 4.1? I looked at old IceCreamCordovaWebViewClient, and I'm thinking that this might not actually work if we add a # behind it.
On Wed, Mar 6, 2013 at 3:33 PM, Joe Bowser <bows...@gmail.com> wrote: > I saw that change, which is why I added the whitelisting. I agree > that there is a depressingly large quantity of 2.3 devices out in the > world, and the fact that you can still buy them means that they're not > going away any time soon. > > On Wed, Mar 6, 2013 at 3:11 PM, Braden Shepherdson <bra...@chromium.org> > wrote: >> I was the one who made this change. We're using it to support >> chrome-extension:// URLs in chrome-cordova. >> >> I think it would work fine for the whitelisting. I'm not sure what it would >> do to our responsiveness, though, to run this for every resource. The >> crippling weakness may be that it was introduced only in API 11 (Honeycomb >> 3.0), and there's a depressingly large quantity of 2.1-2.3 devices still >> out there. >> >> Braden >> >> >> On Wed, Mar 6, 2013 at 5:48 PM, Andrew Grieve <agri...@chromium.org> wrote: >> >>> Sounds like a perfect API for the job! >>> >>> Another thing I am wondering about this API, is if we serve the app from >>> cordova-app://index.html and the use that API to route the requests, will >>> that fix the problem of WebSQL being disabled? Haven't experimented with >>> this yet, but I think Braden was also playing with this API. >>> >>> >>> On Wed, Mar 6, 2013 at 5:23 PM, Joe Bowser <bows...@gmail.com> wrote: >>> >>> > Hey >>> > >>> > Currently there's a major bug in Cordova with respect to the fact that >>> > we can't blacklist any individual web resource. I saw that >>> > shouldInterceptResource was added to CordovaWebViewClient, and I'm >>> > wondering if we can use that to block resources that aren't >>> > whitelisted. >>> > >>> > Anyone used this? And are there any thoughts on this? >>> > >>> > Joe >>> > >>>
