I don’t think so - from how i understand it, everything where you upload a file to a server to edit it there wouldn’t work at all.
The flow looks like this:
You select a file for upload - the browser creates a file in OPFS storage representing the original file - any change you make serverside are replicated to the copy in OPFS storage - when you save the file, you don’t actually have to download it, but the file gets moved from OPFS to wherever you save the file. This prevents long downloads and a lot of warnings (if you would download the file in the classic way, the OS would flag it with the Mark of the Web even tho it is your own file, triggering smartscreen on Windows) and the file in OPFS storage is encrypted because of HTTPS.
I don’t think so - from how i understand it, everything where you upload a file to a server to edit it there wouldn’t work at all.
The flow looks like this:
You select a file for upload - the browser creates a file in OPFS storage representing the original file - any change you make serverside are replicated to the copy in OPFS storage - when you save the file, you don’t actually have to download it, but the file gets moved from OPFS to wherever you save the file. This prevents long downloads and a lot of warnings (if you would download the file in the classic way, the OS would flag it with the Mark of the Web even tho it is your own file, triggering smartscreen on Windows) and the file in OPFS storage is encrypted because of HTTPS.
it’s explained in detail here: https://web.dev/articles/origin-private-file-system