?
On Thursday, March 19, 2020 at 5:54:50 AM UTC+5:30, Michal Novotny wrote:
We plan to remove FTP protocol implementation from our code. This work
is tracked in bug 1574475 [1]. The plan is to
- place FTP behind a pref and turn it off by default on 77 [2]
- keep FTP enabled by default on 78 ESR [3
Hofmann wrote:
Can you share some insight into the usage telemetry that was considered
for unshipping this?
On Thu, Mar 19, 2020 at 9:02 AM Henri Sivonen <mailto:hsivo...@mozilla.com>> wrote:
On Thu, Mar 19, 2020 at 2:24 AM Michal Novotny
mailto:michal.novo...@gmail.com>> w
Yes, it's OS specific, so it depends on what application is registered
to handle FTP URI.
On 3/19/20 10:29 AM, David Teller wrote:
Out of curiosity, what external application? OS-specific?
On 19/03/2020 01:24, Michal Novotny wrote:
We plan to remove FTP protocol implementation from our
Michal Novotny wrote:
We plan to remove FTP protocol implementation from our code.
Chrome's status dashboard says "deprecated" and
https://textslashplain.com/2019/11/04/bye-ftp-support-is-going-away/
said the plan was to turn FTP off by default in version 80. Yet, I
just successf
We plan to remove FTP protocol implementation from our code. This work
is tracked in bug 1574475 [1]. The plan is to
- place FTP behind a pref and turn it off by default on 77 [2]
- keep FTP enabled by default on 78 ESR [3]
- remove the code completely at the beginning of 2021
We're doing this
On 02/19/2014 11:50 AM, Dao wrote:
On 19.02.2014 01:56, Neil wrote:
In particular, I understand
that there is a preference to toggle the cache. What does application
code have to do in order to work with whichever cache has been enabled?
Nothing? It's a different backend behind the same API, a
6 matches
Mail list logo
