• moreeni@lemm.ee
        link
        fedilink
        arrow-up
        25
        arrow-down
        1
        ·
        1 year ago

        8 (!) high impact CVEs fixed. Never forget about the security updates, folks

      • Atemu@lemmy.ml
        link
        fedilink
        arrow-up
        6
        arrow-down
        13
        ·
        1 year ago

        That doesn’t warrant a new version really. That could just be a patch.

          • Atemu@lemmy.ml
            link
            fedilink
            arrow-up
            3
            arrow-down
            2
            ·
            1 year ago

            ESR is for slower feature releases (~annually rather than monthly) that still mostly get regular critical patches in between. That’s an orthogonal topic.

            What I meant is that this “major” version of firefox could have been 116.1.0 rather than 117.0.0 because it didn’t introduce any significant features that could warrant a major version bump, “just” bug fixes.

            • KelsonV@lemmy.world
              link
              fedilink
              English
              arrow-up
              8
              ·
              1 year ago

              They don’t really use the major.minor.bugfix scheme anymore. If they did, they wouldn’t be at version 117.

              I tend to think of them all as minor updates that add up over time, like a rolling release with numbers.

              • Atemu@lemmy.ml
                link
                fedilink
                arrow-up
                2
                ·
                1 year ago

                It’s not semver (that’d put them on, IDK, 4.something maybe) but the versions before the first dot still signifies “significant” to me which this is not.

                That’s not rolling release, that’s still a form of stable releases. You’ll get the feature set of 117 for a month or so with important bugfixes backported from fresher branches. If that ain’t stable, IDK what is. The only truly rolling release of Firefox is Nightly.

    • t�m@lemmy.ml
      link
      fedilink
      arrow-up
      19
      arrow-down
      1
      ·
      1 year ago
      "Support for credit card autofill has been extended to users running Firefox in the IT, ES ,AT, BE, and PL locales.
      
      macOS users can now control the tabability of controls and links via about:preferences.
      Screenshot of new macOS tabability option in about:preferences
      
      To avoid undesirable outcomes on sites which specify their own behavior when pressing shift+right-click, Firefox now has a dom.event.contextmenu.shift_suppresses_event preference to prevent the context menu from appearing."
      

      Other than that yeah

    • Perfide@reddthat.com
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      1 year ago

      As a developer Nested CSS support is a huge QoL improvement. I enabled it manually previously to work on a site assuming that it would be fully supported by time the site launched, so I’m certainly glad they stuck to their roadmap on that.