One of the upcoming updates for the Chrome browser will fully remove support for the FTP protocol. This is stated in a specific document from Google addressing this topic. However, these "innovations" will take effect only a year or later.
The proper support for the FTP protocol in Chrome has always been a sore point for developers at Google. One reason for dropping FTP is the lack of support for secure connections over this protocol in Chromium. Back in 2015, Google developers opened a topic in the official Chromium bug tracker requesting the removal of FTP support. Only recently did they pay attention to this "bug" to completely eliminate FTP components from the browser. Additionally, the company notes that only 0.1% of Chrome users have ever accessed pages with file directories.
Refusal to support the File Transfer Protocol (FTP) , as it is already difficult to use this protocol in Chrome—by default, it is recognized by the browser as insecure and can only be opened with user confirmation. Mozilla shares a similar viewpoint on this data transfer protocol, having added a manual FTP disable feature in Firefox 60. In the subsequent update numbered 61, the loading of resources stored on FTP was blocked.
The complete withdrawal of the protocol is planned to begin in Chrome version 80, which will be released in the first quarter of 2020, and in the following 82nd update, components and code related to FTP will be entirely removed.
Source: 3dnews.ru
