On Thu, Mar 19, 2020 at 09:45:47PM +, Charles Robertson wrote:
> Is there a calendar or somethings that shows future Firefox releases
> Rust requirements? I would like to know what Rust version will Firefox
> 78.0 ESR require when it is released?
There is an outdated one on
https://wiki.mozil
Is there a calendar or somethings that shows future Firefox releases Rust
requirements? I would like to know what Rust version will Firefox 78.0 ESR
require when it is released?
Thanks,
Charles Robertson
___
dev-platform mailing list
dev-platform@lists
As of 2020-03-23 I intend to turn "Document as explicit root of an
intersection observer" on by default on all platforms. It has been
developed behind the
dom.IntersectionObserverExplicitDocumentRoot.enabled preference. Status
in other browsers is: landed in WebKit development build without flag ;
We added the telemetry probes in bug 1579507 [1] to see how many users
still use FTP. The usage was pretty low as you can see in bug 1570155 [2].
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1579507
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1570155#c5
On 3/19/20 10:26 AM, Johann Hof
If you plan to time the unshipping of our FTP support to be after Chrome 81,
then please be aware that Chrome releases are currently paused on Chrome 80.
https://chromereleases.googleblog.com/2020/03/upcoming-chrome-and-chrome-os-releases.html
On Thu, Mar 19, 2020, at 8:56 PM, Michal Novotny wro
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 code.
Would it make sense to ship after Chrome to help ensure this does not lead
to churn?
Also at a time people try to find ways to work from home and share files
(spike of usage in Firefox send), potentially breaking ways people have to
share files may not be good timing?
On Thu, Mar 19, 2020 at 10:42
According to [1], it will be turned off for all users in 81. In 80 it
will be turned off for 1% of users.
[1]
https://docs.google.com/document/d/1JUra5HnsbR_xmtQctkb2iVxRPuhPWhMB5M_zpbuGxTY/edit#heading=h.a4pkgy626xf3
On 3/19/20 9:02 AM, Henri Sivonen wrote:
On Thu, Mar 19, 2020 at 2:24 AM
> We're doing this for security reasons. FTP is an insecure protocol and
> there are no reasons to prefer it over HTTPS for downloading resources.
> Also, a part of the FTP code is very old, unsafe and hard to maintain
> and we found a lot of security bugs in it in the past.
I know this used to b
AFAIU chrome removed all web-observable/web-exposed bits of FTP (e.g.,
navigations, subresources etc.)but still allows top-level navigations
from the user.
Am 19.03.20 um 09:02 schrieb Henri Sivonen:
> On Thu, Mar 19, 2020 at 2:24 AM Michal Novotny
> wrote:
>> We plan to remove FTP protocol imp
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 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
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 wrote:
> On Thu, Mar 19, 2020 at 2:24 AM Michal Novotny
> wrote:
> > We plan to remove FTP protocol implementation from our code.
>
> Chrome's status dashbo
On Thu, Mar 19, 2020 at 2:24 AM 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
13 matches
Mail list logo
