[jira] [Commented] (CB-6045) Expand InAppBrowser scheme to match those of File plugin

["Ram (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CB-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283349#comment-15283349 ] 

Ram commented on CB-6045:
-------------------------

Hi,
In my project, using cordova-plugin-inappbrowser (1.4) from npm packages. I get different results
I use java code to access inbuilt camera/photo libraries
Type Platform Result
_blank iOS 8.3 Can't access camera, but can get to libraries of pictures from the device
_blank iOS 9.3 All works fine: Can access camera, library of pictures from the device
_self iOS 8.3, 9.3, android Nothing works (Network access & Intent: tried *) not sure whether to try https://* or http://* etc.??
_blank android Nothing works
If iOS 8.3 can't access camera within inappBrowser of 1.4, might be an issue at iOS end, but none of the Android (tested 4.4, 4.3, etc..) is NOT working.
Can we get inAppBrowser access to camera & library function similar to iOS please?
Thanks in advance
Reply

> Expand InAppBrowser scheme to match those of File plugin
> --------------------------------------------------------
>
>                 Key: CB-6045
>                 URL: https://issues.apache.org/jira/browse/CB-6045
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Plugin InAppBrowser
>            Reporter: James White
>
> Per http://cordova.apache.org/news/2014/02/10/plugins-release.html, the File plugin changed the way it deals with Entry scheme handling, and allows for additional filesystem abstraction.
> Prior to this update, handling local "content://" type URLs returned from the Camera plugin API, had to be translated to a "file:///" type URL by using the File plugin's window.resolveLocalFileSystemURI() method.  But now that "content://" is a valid file entry scheme, and is understood by DOM methods, etc, window.resolveLocalFileSystemURL() returns the same "content://" URL format, with no way to translate that to a corresponding local "file:///" form.
> Passing a URL with "content://" to the InAppBrowser plugin on Android automatically converts it to something like "http://content://..." making it unable to load such local content directly.
> It would be beneficial for InAppBrowser's support to match the File plugin's supported schemes, beyond the currently supported "file:///" and "http(s)://" schemes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org