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

I was assuming "clips" means that if the new size is larger, the previous (smaller) size is used, so the results appear clipped; i.e. the byte size of the result matches the initial file.size seen. So that's not the case in non-WebKit?

@annevk's questions still need answers:

1. What if the new size is smaller? i.e. does the result have the smaller size, or are padding bytes seen?
3. Is the string clipped or are the bytes clipped before decoding? i.e. for text() and friends, if the string ends with an incomplete UTF-8 sequence, do we see U+FFFD at the end? I'm going to guess yes, but we should test.



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

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