It is not widespread enough to justify continuing to work on it, and making an active decision to not include a feature anymore due to little use is not a bug.

It is not widespread enough to justify continuing to work on it, and making an active decision to not include a feature anymore due to little use is not a bug. The Chrome team published some good information about exactly how widely FTP is used: https://docs.google.com/document/d/1JUra5HnsbR_xmtQctkb2iVxRPuhPWhMB5M_zpbuGxTY/edit https://docs.google.com/document/d/1JUra5HnsbR_xmtQctkb2iVxR... (see heading: Usage information) Removing insecure protocols is a good thing, especially one that is commonly used to download software of all things. If you're one of the ~0.03% (as of late 2020) that relies on downloading files through FTP for whatever reason, there's nothing stopping you from downloading a more specialized client. I truly don't understand what your problem here is: if you install an FTP client and it registers itself as a handler for ftp links with your OS, the process of downloading a file via FTP when you click on an FTP link should be pretty seamless.