[ad_1]
If you’re using Chrome on Windows or other platforms, you may have issues saving files over the network.
For at least the last 10 days, Chrome version 109 (current stable release) has failed when asked to save a file using a Universal Naming Convention (UNC) path. A bug report was submitted on January 17 that Chrome 109.0.5414.94 (32bit) for Windows fails to save files.
Other browsers, notably Apple Safari, Mozilla Firefox, and Microsoft Edge (Chromium-based) seem to be able to complete this task well.
This issue occurs after browsing files online, clicking the save option, and trying to save the data to a network-connected shared device or cloud server. As indicated in the bug report, doing so will result in an error message stating that the package cannot be opened because it contains system files.
However, Windows users aren’t the only ones facing this problem. register I tested a bug demo code submitted by another bug reporter.
The demo code is showOpenFilePicker() Methods that are part of the File System Access API. That particular method allows users to select remotely stored files. On macOS Ventura 13.2 with Chrome version 109.0.5414.119 (arm64) he tried to open a Dropbox file and got the error “Cannot open this file”.
Screenshot of showOpenFilePicker bug in action
Google has been talking about a file system access API since 2019. Formerly known as the Native File System API, that name has been deprecated for “comprehensiveness reasons”.
Prior to that, it was called the Writable Files API. It represents an attempt to give developers a way to allow web apps to access files and directories on the local device.
It’s part of Google’s Project Fugu, which aims to give web apps the same functionality as native platform apps. Apple has been widely accused of undermining that goal with its cowardly development of WebKit-based Safari. But recently, Apple has accelerated browser development to make Safari more competitive, and regulators in Europe and the UK appear poised to force the company to allow rival browsers on iOS. .
The Chrome file bug appears to be somewhere in the file system code of the Blink rendering engine, ideally to be fixed by 31st January 2023, when the version 110 code is scheduled for a stable cut. assigned as Priority increased to 1 because, as a software engineer at Google puts it, “Blocking UNC paths broke many legitimate use cases.” ®
[ad_2]
Source link
