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

Yeah, the Blink behavior makes the most sense to me too. The Gecko way doesn't work when the content changes while keeping the size. The Blink/WebKit way still allows modification when the timestamp doesn't change, but I guess we can safely assume that such files are actively pretending as if no change happened.

(When the timestamp changes and then rolls back to the initial timestamp, Blink/WebKit reject and then allow reading it again. Same for Gecko in terms of file size. An error never means it'll fail forever in all browsers.)

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

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