Fix userVisibility for files in ChromeOS filesystems.

Source/modules/filesystem/FileSystemCallbacks.cpp

Index: Source/modules/filesystem/FileSystemCallbacks.cpp
diff --git a/Source/modules/filesystem/FileSystemCallbacks.cpp b/Source/modules/filesystem/FileSystemCallbacks.cpp
index f0528971d625f64dc282acac9256a8cade129f35..e54bee5eb9fe79f3f845fb7184f68983a068c43f 100644
--- a/Source/modules/filesystem/FileSystemCallbacks.cpp
+++ b/Source/modules/filesystem/FileSystemCallbacks.cpp
@@ -312,19 +312,7 @@ void SnapshotFileCallback::didCreateSnapshotFile(const FileMetadata& metadata, P
     // *after* we've coined a File with a new handle that has the correct type set on it. This allows the
     // blob storage system to track when a temp file can and can't be safely deleted.
 
-    // For regular filesystem types (temporary or persistent), we should not cache file metadata as it could change File semantics.
-    // For other filesystem types (which could be platform-specific ones), there's a chance that the files are on remote filesystem. If the port has returned metadata just pass it to File constructor (so we may cache the metadata).
-    // FIXME: We should use the snapshot metadata for all files.
-    // https://www.w3.org/Bugs/Public/show_bug.cgi?id=17746
-    if (m_fileSystem->type() == FileSystemTypeTemporary || m_fileSystem->type() == FileSystemTypePersistent) {
-        handleEventOrScheduleCallback(m_successCallback.release(), File::createForFileSystemFile(metadata.platformPath, m_name));
-    } else if (!metadata.platformPath.isEmpty()) {
-        // If the platformPath in the returned metadata is given, we create a File object for the path.
-        handleEventOrScheduleCallback(m_successCallback.release(), File::createForFileSystemFile(m_name, metadata));
-    } else {
-        // Otherwise create a File from the FileSystem URL.
-        handleEventOrScheduleCallback(m_successCallback.release(), File::createForFileSystemFile(m_url, metadata));
-    }
+    handleEventOrScheduleCallback(m_successCallback.release(), DOMFileSystemBase::createFile(metadata, m_url, m_fileSystem->type(), m_name));
 }
 
 // VoidCallbacks --------------------------------------------------------------