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
The validator website includes the message that "Note: Selecting a dataset only performs validation. Files are never uploaded."
However, when data is selected for upload the browser counters with something like this (Chrome):
Or like this (Firefox):
As noted by @robertoostenveld, this is not in the validator code-base, but comes from the browser itself. The question is whether there is any way to prevent the browser from raising this, or some other way to mitigate this.
The text was updated successfully, but these errors were encountered:
There isn't a way to avoid this while targeting the browser since you are exposing the files to network loaded JavaScript that could do anything with them. We may be able to slightly improve how this looks to a user by accessing via the File System Access API instead of a input form element but this API is Blink only at the moment and I think that makes it unsuitable for the validator. Here's an example of asking for read only access to a directory looks like with this API though in case it gains wider browser support (screenshot from Chrome).
There's some specification level discussion of adding support for installed PWAs to persist filesystem permissions but I don't expect it to be implemented anytime soon. For now, an installed PWA just shows the same permission request as any other webpage when prompting for the filesystem access and asks each time it is opened.
effigies
transferred this issue from bids-standard/legacy-validator
Nov 5, 2024
The validator website includes the message that "Note: Selecting a dataset only performs validation. Files are never uploaded."
However, when data is selected for upload the browser counters with something like this (Chrome):
Or like this (Firefox):
As noted by @robertoostenveld, this is not in the validator code-base, but comes from the browser itself. The question is whether there is any way to prevent the browser from raising this, or some other way to mitigate this.
The text was updated successfully, but these errors were encountered: