Announcement

Collapse
No announcement yet.

Firefox 132 Ready With Certificate Compression, Accelerated SVG Filter Primitives

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

  • Firefox 132 Ready With Certificate Compression, Accelerated SVG Filter Primitives

    Phoronix: Firefox 132 Ready With Certificate Compression, Accelerated SVG Filter Primitives

    Mozilla Firefox 132.0 release builds are now available for Linux, macOS, and Windows for this newest monthly feature release to this open-source web browser...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    HTTP-only favicons are now blocked if they cannot be received over HTTPS when accessing an HTTPS site
    Why? What exactly would be the security concern in this?

    Comment


    • #3
      And another release where the Firefox developers ignore the fact that Firefox uses a crappy GTK file picker, even on Qt-based DEs!
      And they also ignore the fact that a lot of mobile phones record videos in HEVC format, which we cannot put on a NextCloud server as Firefox will just ignore them and not let us to play them.
      Even if we have FFmpeg installed and they could be decoded by it!

      As for people saying that's a legal issue, the how the fuck we are able to record them in HEVC format and play them on the phone?
      And how come Firefox cannot relse such support, disabled by default and the ones of us who have recorded their personal vidoes in HEVC format and put them on our NextCloud server to turn it on?
      Who the fuck would say anything to Mozilla when Firefox would came with such a feature disable by default and when it's enabled, it uses the system to decode those videos?

      Let me guess, for the missing HDR support, they blame some bollocks legal issues too?
      Fuck you Mozilla for keep pouring a shit ton of money into the CEO instead of paying developers to bring the missing features!

      Comment


      • #4
        Originally posted by Nuc!eoN View Post

        Why? What exactly would be the security concern in this?
        The same concerns that always affected mixed HTTP content on HTTPS sites. Theoretically a man-in-the-middle could spoof the favicon. Honestly, this is something that should have been done a long time ago as is already the case with scripts and images.

        Comment


        • #5
          Originally posted by Danny3 View Post
          And another release where the Firefox developers ignore the fact that Firefox uses a crappy GTK file picker, even on Qt-based DEs!
          This is solved by portals.

          Originally posted by Danny3 View Post
          And they also ignore the fact that a lot of mobile phones record videos in HEVC format, which we cannot put on a NextCloud server as Firefox will just ignore them and not let us to play them.
          Even if we have FFmpeg installed and they could be decoded by it!

          As for people saying that's a legal issue, the how the fuck we are able to record them in HEVC format and play them on the phone?
          And how come Firefox cannot relse such support, disabled by default and the ones of us who have recorded their personal vidoes in HEVC format and put them on our NextCloud server to turn it on?
          Who the fuck would say anything to Mozilla when Firefox would came with such a feature disable by default and when it's enabled, it uses the system to decode those videos?
          HEVC support requires an expensive license, even on Chrome they only support it for devices with hardware acceleration. That's no good, I need to be able to play it back on hardware that lacks hardware decoding too. It's much better to use free formats if you can. You should be able to losslessly transcode it with Ffmpeg to something better (AV1 or VP9 or the trusty .h264 that works everywhere).

          web browser compatibility support html css svg html5 css3 opera chrome firefox safari internet explorer


          Originally posted by Danny3 View Post
          Let me guess, for the missing HDR support, they blame some bollocks legal issues too?
          Fuck you Mozilla for keep pouring a shit ton of money into the CEO instead of paying developers to bring the missing features!
          HDR support has to be done in Gecko first. It's an ongoing effort:


          Linux is now officially moving faster than the web.
          Last edited by ahrs; 28 October 2024, 12:22 PM.

          Comment


          • #6
            Originally posted by Nuc!eoN View Post

            Why? What exactly would be the security concern in this?
            It would also unmask the site you want to visit.

            Comment


            • #7
              Originally posted by ahrs View Post
              You should be able to losslessly transcode it with Ffmpeg to something better (AV1 or VP9 or the trusty .h264 that works everywhere)..
              Unfotunately, lossless transcoding is not possible since it's an entirely different codec (not just a different container format). There will always be some quality loss involved, unless you use a true lossless format as a target (which creates huge files).

              Comment


              • #8
                Originally posted by Calinou View Post

                Unfotunately, lossless transcoding is not possible since it's an entirely different codec (not just a different container format). There will always be some quality loss involved, unless you use a true lossless format as a target (which creates huge files).
                And that's exactly I don't want and I try to avoid!
                Besides more wasted time and keeping all files 2 times (duplicates) as for sure I don't want to delete the original ones that have the best quality.

                Comment


                • #9
                  Originally posted by Calinou View Post
                  Unfotunately, lossless transcoding is not possible since it's an entirely different codec (not just a different container format). There will always be some quality loss involved, unless you use a true lossless format as a target (which creates huge files).
                  Of course, in "THEORY" it is impossible to achieve exactly 100% the same quality.
                  But in "PRACTICAL" cases, this is possible to 99% and your eyes won't see much difference.

                  Comment


                  • #10
                    Originally posted by ahrs View Post
                    HDR support has to be done in Gecko first. It's an ongoing effort:
                    Because dev resources are chaotically spread due to poor project management?
                    How much would it cost to fund a dev who doesn't work on anything else until it's done? Why is this not done? When will it ever be finished?
                    And lastly: Is it futile to wait any longer for Mozilla getting their crap together and maybe just dump them in favor of any Chromium-based browser? At least every day more people come to that conclusion.

                    Comment

                    Working...
                    X