Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)

q2p left a comment (w3c/FileAPI#203)

> Any updates on this?

Web standards take a lot of time. Last time I filed a request in middle school, it took until graduating collage to fix ONE flexbox attribute.
Here's how it usually goes:
1. Implement a terrible API
2. Guys this API sucks, let's use this one.
3. Well darn maybe the third time's the charm?
4. Finally all vendors have agreed on the forth standard
5. Sorry, no updated, the existing APIs are too difficult to reconcile, the code is a mess, we spend 400mb of ram just to track blob states oopises. However, if you really want the feature, here's a 2000 loc workaround for chrome and a 4000 loc workaround for firefox that works only on saturdays 50% of the time.

One day `chrome.download { filename }` will actually keep the download name. Maybe. If they remember and don't forget. I wouldn't count on that.

As a workaround you can perform an RCE to spawn a local python proxy and pipe your file to it to set the name through `Content-Disposition`. That's in W3C style)

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

Message ID: <w3c/FileAPI/issues/203/5107347420@github.com>