Its not just Chrome, Firefox is planning to deprecate it as well (https://www.bleepingcomputer.com/news/google/chrome-and-fire...). Relevant Bugzilla ticket (http://bugzilla.mozilla.org/show_bug.cgi?id=85464)
Bugzilla.mozilla.org is offline, here's a mirror: https://web.archive.org/web/20190520010425/http://bugzilla.m...
and relevant quotes posted there (a year ago!): "I think we should mark this bug as WONTFIX. We have a vague plans of deprecating FTP completely in Firefox, there is no point in adding more code in this area." "Since we (sooner or later) would like to deprecate FTP completely, we should not add more code in that area to our codebase."
Mozilla has lost the ability to be an independent protector of the Open Web
And to the people who disagree: Firefox has always been great, but it often came with a lot of bugs and inconveniences. It didn't use to be as accessible.
I tried to switch to FF on multiple occasions, but it's a CPU hog on MacBook. Why is this issue ignored for so long?
From what I understand, it's a low level rendering issue.
Source: I wrote the initial version of those patches, though I think Markus has basically rewritten them all at this point.
Please explain how. Since firefox 57 (quantum), there's precisely no way to do that properly...
It has been going on for years.