Announcement

Collapse
No announcement yet.

Chrome 121 Adds New CSS & WebGPU Features

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

  • Chrome 121 Adds New CSS & WebGPU Features

    Phoronix: Chrome 121 Adds New CSS & WebGPU Features

    In addition to Firefox 122 making it to stable today, Google has also promoted their Chrome 121 web browser to its stable channel...

    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
    Does this release include VA-API support on Ozone/Wayland?

    Comment


    • #3
      VA-API support fixed in Xorg while Vulkan is default.

      Comment


      • #4
        It also has HDR improvements https://developer.chrome.com/blog/ne...re_color_space
        Linux Desktop HDR can't come soon enough.

        Comment


        • #5
          Originally posted by EvilHowl View Post
          Does this release include VA-API support on Ozone/Wayland?
          I think it's gonna be included into the next release, 122. At least that's what another member said on the Ozone/Wayland VA-API support thread.

          Comment


          • #6
            Originally posted by EvilHowl View Post
            Does this release include VA-API support on Ozone/Wayland?
            Just tested, unfortunately No.

            Comment


            • #7
              Originally posted by chromer View Post
              VA-API support fixed in Xorg while Vulkan is default.
              You mean Chrome now runs on Vulkan by default instead of OpenGL?

              Comment


              • #8
                Originally posted by chromer View Post
                VA-API support fixed in Xorg while Vulkan is default.
                Is it working for you? Here it continues to show over 30% CPU utilization (Ryzen 5600) on YT 4k/60fps video, on X-Org. Firefox on the other hand, do have the acceleration working fine.

                Comment


                • #9
                  Originally posted by user1 View Post

                  You mean Chrome now runs on Vulkan by default instead of OpenGL?
                  It's enabled based on platform support, but you can enable it via flags : --enable-features=Vulkan,VulkanFromANGLE,DefaultANGLEVulkan .
                  Pre-121 when Vulkan was default VAAPI was broken, now in 121 this is fixed.

                  Comment


                  • #10
                    Originally posted by M@GOid View Post

                    Is it working for you? Here it continues to show over 30% CPU utilization (Ryzen 5600) on YT 4k/60fps video, on X-Org. Firefox on the other hand, do have the acceleration working fine.
                    It's working fine on Intel hardware, here i have Coffe-lake.

                    Comment

                    Working...
                    X