Re: [w3c/FileAPI] Remove the / -> : replacement from the File constructor (#41)

Replacing rather than throwing does seem bad and Entries API does indeed only produce File objects, it doesn't appear to consume them. Entries API does appear to define a model for files in https://wicg.github.io/entries-api/#names-paths onward and that does conflict with allowing various code points in the name, including `/`. And its processing model does seem to get confused if a name with `/` would appear as it deals with paths as single strings.

Looking at this I think a reasonable outcome would be:

1. Remove the replace operation from File API and Firefox. And add/change a test.
2. File an issue against Entries API to ensure it's model for files is aligned with File API. We shouldn't have multiple conflicting models of what files are in the web platform.

-- 
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/41#issuecomment-638062015