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

> What do you mean? You can create a new File object. When a file is "renamed" the file is changed anyway, correct?

See, you said "File object" automatically instead of "File instance" because it is not an instance. It is some kind of **FileData** /**FileBlob** etc.

I want `new File(...).setName('file')`. I saw this code as `new FileWrapper().setName('file').toNativeFile()` in many closed source projects, that I can't show. Today I saw it again. Each project has its own bicycle wrapper with its own terminology and complexity. Developers of this "File" interface should know about this situation. Why not?

-- 
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#issuecomment-480950086

Received on Monday, 8 April 2019 18:29:36 UTC