Github user martincgg commented on the pull request:
https://github.com/apache/cordova-mobile-spec/pull/76#issuecomment-46960316
Hi @purplecabbage ,
I've been working on the File API and the mobile spec test as well, this
specific PR, the native side is not returning the path with the URL-encoding as
%20, I thought that it was totally acceptable if spaces were returned instead.
Let me report some of my findings:
In the image at left is mostly after this fix:
https://issues.apache.org/jira/browse/CB-6980
in the right that was before of it. Several were failing because
resolveLocalFileSystemURI it was losing information about the filesystem
property.
The first square marked on the image it belongs to 4 tests (spec 67, 68, 69
and 78) which are failing when a file is moved and the filesystem information
is lost at some point, the issue related is CB-6901.
The second square is related with support of readAsBinaryString &
readAsArrayBuffer, issues CB-6988 & CB-6989, I've been working to setup those
methods on the native side.
The third square is related with the issue CB-6923 (I'm working on that one
too), the native side is not able to handle the resolve navigation a parent
directory using a relative path, e.g.:
fileName = ../resolve.file.uri
I'll continue working on those issues
About the mobile spec conditions some of them are about join paths for
Windows Phone and some others are to compare the path retrieved from the native
side something like: //native instead of file://.
Tests on Windows Phone 8 & 8.1 emulator as well as physical device, both
are consistent behavior related with the mentioned issues.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
