Firefox 134 Available With Experimental HTML "autocorrect" Attribute

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67408

    Firefox 134 Available With Experimental HTML "autocorrect" Attribute

    Phoronix: Firefox 134 Available With Experimental HTML "autocorrect" Attribute

    Mozilla has published the Firefox 134.0 release binaries today ahead of their official release tomorrow. This first Firefox update of 2025 brings a few new features to Linux users and those on other platforms...

    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
  • Anux
    Senior Member
    • Nov 2021
    • 1960

    #2
    while this autocorrect attribute can allow web developers to specify whether this auto-correction behavior should be applied to a given from or HTML field.
    Hu? Shouldn't the user be the one to decide if he wants auto-correct or not?

    Comment

    • Jabberwocky
      Senior Member
      • Aug 2011
      • 1212

      #3
      I'm I reading this correctly? 0 New features, 0 fixes for Linux Desktop in a major release.

      Comment

      • Jaxad0127
        Senior Member
        • Oct 2018
        • 220

        #4
        Originally posted by Anux View Post
        Hu? Shouldn't the user be the one to decide if he wants auto-correct or not?
        Some input types (like file names or coupon codes) shouldn't be spell checked.

        Comment

        • Jaxad0127
          Senior Member
          • Oct 2018
          • 220

          #5
          Originally posted by Jabberwocky View Post
          I'm I reading this correctly? 0 New features, 0 fixes for Linux Desktop in a major release.
          The touchpad hold gesture is new for Linux.

          Comment

          • carguello2
            Phoronix Member
            • Oct 2023
            • 51

            #6
            Windows users with Firefox 134 meanwhile now have H.265/HEVC hardware accelerated support...
            We already had HEVC decoding on Windows with supported hardware?

            image.png

            Comment

            • blackshard
              Senior Member
              • Oct 2009
              • 603

              #7
              Originally posted by Anux View Post
              Hu? Shouldn't the user be the one to decide if he wants auto-correct or not?
              the HTML developer decides if autocorrect is sensible for the input field, then the user may decide if he/she wants autocorrect

              Comment

              • carguello2
                Phoronix Member
                • Oct 2023
                • 51

                #8
                Originally posted by carguello2 View Post

                We already had HEVC decoding on Windows with supported hardware?

                image.png
                Nothing has changed between 133.0.3 and 134.0 now,

                image.png

                Comment

                • carguello2
                  Phoronix Member
                  • Oct 2023
                  • 51

                  #9
                  Originally posted by carguello2 View Post

                  Nothing has changed between 133.0.3 and 134.0 now,

                  image.png
                  Surprisingly,
                  https://thorium.rocks/misc/h265-tester.html, both videos failed to load on Firefox... Brave, Chrome and Edge all worked just fine.

                  Comment

                  • Danny3
                    Senior Member
                    • Apr 2012
                    • 2422

                    #10
                    Well, fuck you Mozilla for offering hardware accelerated HEVC decoding just for Windows user!
                    I've set my phone to record the 4K @ 60 FPS videos in HEVC (H.265) instead of AVC (H.264) and I'm not willing to go back from that or to convert my collection of personal videos.
                    So screw you suggesting me that I should use the codec with the worse quality and bigger file size or to convert them, which of course will also mean worse quality!

                    But hey, lets reward the CEO with a huge monthly salary...

                    Comment

                    Working...
                    X