Re: [w3c/FileAPI] Define WebKit's underlying file changes behavior (#47) from Kagami Sascha Rosylight on 2022-05-20 (public-webapps-github@w3.org from May 2022)

From: Kagami Sascha Rosylight <notifications@github.com>
Date: Fri, 20 May 2022 04:45:28 -0700
To: w3c/FileAPI <FileAPI@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/FileAPI/issues/47/1132803750@github.com>

>If normally the timestamp would change I'd actually prefer that we irrevocably lose access on changes, but perhaps that's hard to implement?

I think the change is only observed when reading the file, and that means if the timestamp changes and then rolls back before reading then the browser won't notice whether such change even happened. I'd say it would be inconsistent to let changes happen only in some situations.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/47#issuecomment-1132803750
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/issues/47/1132803750@github.com>

Received on Friday, 20 May 2022 11:45:40 UTC