[w3c/FileAPI] Readonly attributes without setters? (#126)

You made all attributes readonly for File API. But you don't want to provide any setters. People have to recreate File object just to change one attribute and loose performance.

Where is `setName`, `setLastModified`, `setType`, `setSize`, etc?

Do authors of this spec have any functional fetish? It makes your API unusable for people without that fetish.

Is there any real reason to keep File API without setters? Any other JS APIs have all possible setters available.

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