You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if that's intended as-is, but when calling getDirectory with undefined in chrome, chrome calls the callback with the same DirectoryEntry on which getDirectory was called on.
Calling getDirectory with undefined is probably always a bug, in order to be in line with chrome the shim should follow it's behaviour though, not sure which way is better.
The text was updated successfully, but these errors were encountered:
I couldn't find any exact specification in the W3C definition.
It says Otherwise, if no other error occurs, getDirectory must return a DirectoryEntrySync corresponding to path. though, not sure if undefined as argument is an error.
Not sure if that's intended as-is, but when calling getDirectory with undefined in chrome, chrome calls the callback with the same DirectoryEntry on which getDirectory was called on.
Calling getDirectory with undefined is probably always a bug, in order to be in line with chrome the shim should follow it's behaviour though, not sure which way is better.
The text was updated successfully, but these errors were encountered: