boredom2 opened a new issue #1361:
URL: https://github.com/apache/cordova-android/issues/1361


   # Bug Report
   
   ## Problem
   
   We are creating local Image files, that should be displayed in an <img 
src="LOCAL" />
   Until cordova 9, that worked with "file:///..." (and CSP including file:, 
filesystem: and cdvfile:)
   
   ### What is expected to happen?
   
   Images should load the local File - with "file:///" URL or at least with 
cdvfile:// URL.
   
   ### What does actually happen?
   
   Now, "file:" does not work at all (not allowed to load) - after converting 
the local ULR to a cdvfile though, the Request dies with 
"net::ERR_UNKNOWN_URL_SCHEME"
   
   If I set "AndroidInsecureFileModeEnabled" to TRUE, everything is working 
again fine. But I would really prefer to not use this Setting for other 
reasons. These Images are the only time, the WebView comes in contact with 
local Files.
   
   
   ### Environment, Platform, Device
   all devices
   
   ### Version information
   Cordova 10 on android 11, android 12 Beta 4.
   
   ## Checklist
   <!-- Please check the boxes by putting an x in the [ ] like so: [x] -->
   
   - [x] I searched for existing GitHub issues
   - [x] I updated all Cordova tooling to most recent version
   - [x] I included all the necessary information above
   
   I was able to solve this by a very annoying hack - i use Cordova Filesystem 
Methods to create a data: String out of the File. But thats very 
time-consuming, ugly and complicated to handle with a lot of Files. Do I missed 
some kind of Setting or anything similar, that stops this Functionality from 
working?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to