1. 40

  2. 9

    I can confirm that the Firefox Development build does feel much snappier than the latest stable release even though its performance has already increased a lot this year (e.g. multi-processing).

    1. 2

      A small tip for Linux users:

      If you want to run both version side-by-side you need to have separate Firefox profiles. A new profile can be created by running $ firefox --ProfileManager and it will be located in ~/.mozilla/firefox/<some-hash>.<profile-name>.

      Then you need to specify the profile to use in the Exec directive of the desktop file. I just simply copied the desktop file from the package into ~/.local/share/applications/ so I don’t need to edit the original:

      diff /usr/share/applications/firefox-developer.desktop ~/.local/share/applications/firefox-developer.desktop 
      < Exec=firefox-developer --class=firefox-developer %u
      > Exec=firefox-developer --class=firefox-developer ~/.mozilla/firefox/1234abcd.dev-edition-default %u
    2. 7

      Super random: this release also features a new verse from the Book of Mozilla. I used to love these tiny easter eggs in the early days of Firefox:

      The Beast adopted new raiment and studied the ways of Time and Space and Light and the Flow of energy through the Universe. From its studies, the Beast fashioned new structures from oxidised metal and proclaimed their glories. And the Beast’s followers rejoiced, finding renewed purpose in these teachings

      No idea if it’s always been like that, but it’s interesting that they use HTML entities to render the page:

        <p id="moztext">
        <p id="from">

      These seem to be defined on chrome://global/locale/mozilla.dtd. Sounds like a useful technique for localization, albeit one I’ve never ever heard of. Does anyone have any insights on this?

      1. 5

        Really disappointing how they crippled the extension mechanism: https://github.com/lusakasa/saka-key/issues/53

        The justification of “it’s for security” makes no sense.

        1. 5

          In my view, it’s a bug in the browser if important keybindings can be overridden by content.

          1. 7

            I agree, if by “content” you mean web pages.

            However, the idea that web extensions I’ve explicitly given permission to install can override the “new tab” shortcut which I use many times a day, but not the “new window” shortcut which I haven’t used on purpose in several years is daft, and blaming it on “security” is scaremongering.

            1. 2

              Vivaldi has a brilliant ‘Toggle keyboard shortcuts’ action that you can bind to a shortcut (or mouse gesture). It’s a pity that it disables the browser’s bindings instead of the website’s, but even then I find it useful.

              For that matter, extensions unpreventably overriding browser defaults is as silly as web content doing so. I hope Firefox and Chrome and … Edge, is it? can one day afford to overhaul their keybindings architecture, so that:

              • the web browser and extensions expose actions (plus desired bindings)
              • a central keybinding registry lets you bind available actions to keys
              • website Javascript can be kept in its proper place: subordinate to the user and their browser. We run tings. Tings nuh run we.
              1. 2

                The setup you’ve described is so obviously the right way to handle this problem that I have to ask myself, did browser vendors consider this and reject it as impractical, or did it honestly just not occur to them to come up with a sensible, declarative way to handle key bindings?

            2. 1

              Yeah, the “web extensions” garbage is very sad

              1. 11

                ? At first, I was sad about this move too but after upgrading, I managed to find alternatives for most of the plugin I was really using. I feel like it’s a new start for browser plugin development now and I think some people will consider doing a rewrite of popular projects which could be a good thing in the end. Don’t fix what’s not broken they say, but I don’t think there are only downsides about this move.

                This change actually made me learn part of the webextensions api and I started working on a webextensions history browser plugin because the orher similar plugin I was using wasn’t open source and I didn’t like its ui.

                I hope this won’t block users from adopting the new versions. I really like the recent overall improvements in firefox ?

            3. 4

              I’m on the beta now and it is much faster. Unfortunately, my laptop’s fans are spinning at full speed.

              1. 1

                i’ve noticed that some webapps (like telegram) tend to do that if they run long enough, after closing the tabs cpu usage goes back to normal.

              2. 3

                I’ve really been enjoying Nightly, super fast and I eventually liked the UI changes. (I initially missed the curved tabs)

                1. 1

                  Anyone seeing noticeable font rendering differences between Firefox and Chrome (Debian). Seems like Firefox has less or no anti aliasing.

                  1. 1

                    FreeBSD users: my ports fork has www/firefox-beta now :)