Google company deprecation of FTP support in Chromium and Chrome. In Chrome 80, slated for early 2020, phasing out FTP support for stable branch users (for enterprise deployments, a DisableFTP flag will be added to bring back FTP). In Chrome 82, it is planned to completely remove the code and resources used to provide the FTP client.
FTP support began to be phased out in Chrome 63, in which
accessing resources via the FTP protocol began to be marked as an insecure connection. In Chrome 72, displaying the contents of resources downloaded via the "ftp://" protocol was disabled in the browser window (for example, it stopped showing HTML documents and README files), and it was forbidden to use FTP when downloading sub-resources from documents. In Chrome 74, access to FTP through an HTTP proxy stopped working due to a bug, and in Chrome 76, proxy support for FTP was removed. At the moment, downloading files via direct links and displaying the contents of directories remain functional.
According to Google, FTP is almost not used anymore - the share of FTP users is about 0.1%. This protocol is also insecure due to the lack of traffic encryption. Support for FTPS (FTP over SSL) for Chrome is not implemented, and the company does not see the point in finalizing the FTP client in the browser, taking into account its lack of demand, and also does not intend to continue maintaining an insecure implementation (in terms of lack of encryption). If it is necessary to download data via FTP, users will be prompted to use third-party FTP clients - when trying to open links via the βftp://β protocol, the browser will call the handler installed in the operating system.
Source: opennet.ru