[
https://issues.apache.org/jira/browse/CB-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James White updated CB-6045:
----------------------------
Description:
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.
was:
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://...";
It would be of benefit for InAppBrowser's support to expand beyond the current
"file:///" and "http(s)://" schemes.
> 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.1.5#6160)
