Re: [w3c/FileAPI] Define WebKit's underlying file changes behavior (#47)

Just started looking at this. Per my latest observation:

1. `file.text()` on all of Gecko, Blink, and WebKit clips the returned string by the initial file size when the file size changes.
2. `file.text()` on Blink and WebKit rejects when the timestamp changes. It does not on Gecko.
3. `fileReader.readAsBinaryString()` on Gecko fires an error event when the file size changes. It does not care about the timestamp.
4. `fileReader.readAsBinaryString()` on Blink and WebKit fires an error when the timestamp changes. If the size changes, it clips the returned string.
5. `file.size` never changes in all browsers.
6. `file.lastModified` never changes in Gecko and Blink. WebKit seemingly just reports the current time, ignoring the actual data?

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

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