Announcement

Collapse
No announcement yet.

Firefox 90 Released With FTP Support Removed, Better WebRender Software Performance

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Mozilla T.Fox ESR never made more sense. But at some point it will become one of the 90's series.

    Where can we go after T.Fox dies then?

    Comment


    • #32
      Originally posted by qlum View Post
      Ultimately it is not the browsers job to do everything, handling ftp should fall outside it's job description.
      Firefox also does not handle other file transfer protocols such as SFTP or SMB, so why should it support ftp?
      At the very least for me it has never been something I would use a webbrowser for.
      FTP support is a relic from the time when Internet Explorer was basically an extended version of the Explorer file browser, which happened to have primitive FTP support included. So I guess other browser vendors felt obligated to offer even more primitive support as well.

      Comment


      • #33
        The UI is totally messed up on my high-DPI display after upgrading to Firefox 90. It seems to have gained some more-native support for high DPI from GTK3, since my old hacks made everything twice the size initially. But now everything is too small and too blurry. I cannot get the UI to look as crisp as it did in past versions with my own scalability configurations.

        Comment


        • #34
          Originally posted by bachchain View Post
          I would expect a web browser to only include functionality needed for browsing the web, which has always meant HTML documents. To have it support other application protocols sounds like a violation of the Unix Philosophy
          Ah, that common mistake.
          WWW is not http/https. WWW works o URLs. https://www.mysite.com is an URL, but so is ftp://mysite.com/gimme_my_file.pdf

          That's why I said drawing a line is complicated (and largely arbitrary)

          Originally posted by jacob View Post
          It meant more code to maintain that barely anyone ever used.
          FTP has been done for over a decade, I doubt there was much there to maintain. But it's possible the code was messy, in which case I understand the desire to get rid of it.
          Last edited by bug77; 14 July 2021, 08:24 AM.

          Comment


          • #35
            Originally posted by emblemparade View Post
            average user may not see if it's being used on a page. The issue is not about typing an "ftp://" URL directly, which means that you know what you're doing, but what if a malicious web site incorporates references or links to FTP URLs? You might be browsing the web as usual and not even realize that you're using FTP. That's kinda terrifying.
            How is that different from https "page" referencing http? It would be just enough to don't allow loading content from ftp on https sites.

            My Brother device uploads scanned documents to the local FTP server. I can't get them using Firefox but at least I can feel safe now.

            Comment


            • #36
              Firefox crashes under wayland for me on Manjaro. And apparently for some arch users as well.
              Might be distro-specific but it's broken after the update.

              Comment


              • #37
                Originally posted by verude View Post
                When it was announced they were going to remove FTP some months ago, I switched to dolphin, and I've had no issues with it for my simple usecases.
                Thank you! Exactly the sort of answer I came looking for.

                Comment


                • #38
                  Originally posted by Mez' View Post
                  Firefox crashes under wayland for me on Manjaro. And apparently for some arch users as well.
                  Might be distro-specific but it's broken after the update.
                  I am an Arch user and it did indeed crash after upgrade. Incidentally I had a "system accident" at the same time and had to do some manual restoration work. After this Firefox did actually start. So I have no idea what was wrong on the first try. There was a GTK update at the same time and Firefox is leveraging GTK more than before, maybe there was some version incompatibility there, since initially I only upgraded Firefox and not the other few packages waiting in queue.

                  Comment


                  • #39
                    Originally posted by curfew View Post
                    I am an Arch user and it did indeed crash after upgrade. Incidentally I had a "system accident" at the same time and had to do some manual restoration work. After this Firefox did actually start. So I have no idea what was wrong on the first try. There was a GTK update at the same time and Firefox is leveraging GTK more than before, maybe there was some version incompatibility there, since initially I only upgraded Firefox and not the other few packages waiting in queue.
                    Well, it's really strange.

                    On Xorg, everything works alright.

                    On wayland:
                    • nightly works perfectly
                    • 90 doesn't work
                    • 90 works in safe mode
                    • Yet 90 doesn't work with extensions and CSS deactivated
                    Usually if it works in safe mode, then an extension or the CSS is causing the issue. Here, I'm a bit baffled.

                    Comment


                    • #40
                      Solved.

                      Comment

                      Working...
                      X