Firefox 135 Published With Safeguards To Prevent Overwhelming The Back History

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

    Firefox 135 Published With Safeguards To Prevent Overwhelming The Back History

    Phoronix: Firefox 135 Published With Safeguards To Prevent Overwhelming The Back History

    Mozilla Firefox 135 release binaries are now available for those wanting to grab the latest browser release right away...

    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
  • andyprough
    Senior Member
    • Feb 2012
    • 2453

    #2
    Firefox 135 on macOS and Linux also now provides the option to close only the current tab if the quit keyboard shortcut is used when multiple tabs are open in the window.
    This sounds super annoying if it works like it sounds like it will work. If I hit Ctrl-q, I want the program to quit, I don't want a dialog asking me what part of the program I want to close.

    Comment

    • bug77
      Senior Member
      • Dec 2009
      • 6519

      #3
      Originally posted by andyprough View Post

      This sounds super annoying if it works like it sounds like it will work. If I hit Ctrl-q, I want the program to quit, I don't want a dialog asking me what part of the program I want to close.
      I wouldn't worry too much, there's probably a "remember my option" checkbox in there.

      Comment

      • treba
        Senior Member
        • Sep 2012
        • 716

        #4
        This version also fixes opaque regions on Wayland/X11 which broke a few versions ago. This can be visible on setups with weak GPUs and high resolutions, like older Intel on 4k.

        Comment

        • chuckula
          Senior Member
          • Dec 2011
          • 846

          #5
          Originally posted by treba View Post
          This version also fixes opaque regions on Wayland/X11 which broke a few versions ago. This can be visible on setups with weak GPUs and high resolutions, like older Intel on 4k.
          In that case my RX 7800 is "weak" too because it shows that effect.

          Comment

          • Old Grouch
            Senior Member
            • Apr 2020
            • 696

            #6
            This is nice.

            The websites that incorporate deleting the tab-history for their tab are very annoying.

            So are the ones that show up on internet search engines with a deep link, which auto-redirects to the top-level home/greeting page if you try and use it.

            Comment

            • treba
              Senior Member
              • Sep 2012
              • 716

              #7
              Originally posted by chuckula View Post

              In that case my RX 7800 is "weak" too because it shows that effect.
              Oh wow, you see a visible difference in performance / less frame drops with 135 compared to 134 on that beefy GPU? Edit: serious question, I would have assumed it shouldn't be visible there.
              Last edited by treba; 03 February 2025, 12:34 PM.

              Comment

              • ssokolow
                Senior Member
                • Nov 2013
                • 5108

                #8
                Originally posted by andyprough View Post

                This sounds super annoying if it works like it sounds like it will work. If I hit Ctrl-q, I want the program to quit, I don't want a dialog asking me what part of the program I want to close.
                They'll probably hang it off the existing "Ask for confirmation on Ctrl-Q" option which people like me lobbied hard for and, in the interim, actually wrote workarounds for.

                (In my case, a python-xlib script which watched which window had focus and used XGrabKey to swallow Ctrl-Q if Firefox was focused.))

                Comment

                • intelfx
                  Senior Member
                  • Jun 2018
                  • 1146

                  #9
                  Originally posted by treba View Post
                  This version also fixes opaque regions on Wayland/X11 which broke a few versions ago. This can be visible on setups with weak GPUs and high resolutions, like older Intel on 4k.
                  If you don’t mind reminding me, what classes of optimizations does that generally enable?

                  Comment

                  • treba
                    Senior Member
                    • Sep 2012
                    • 716

                    #10
                    Originally posted by intelfx View Post

                    If you don’t mind reminding me, what classes of optimizations does that generally enable?
                    Firefox, like most CSD apps, uses a RGBA format (with alpha channel) for its content in order to draw rounded corners etc. The opaque region is a hint for compositors about opaque parts of the surface, so they can avoid drawing the background etc - basically avoiding all the additional cost compared to using a non-alpha format. In fullscreen it additionally means compositors can do direct-scanout ("passthrough") with a single hardware plane / without needing overlay planes (and most compositors don't even support overlay planes yet). In short: this should reduce GPU bandwidth usage quite a bit in most common scenarios.

                    For context, see wl_surface::set_opaque_region or _NET_WM_OPAQUE_REGION
                    Last edited by treba; 03 February 2025, 01:43 PM.

                    Comment

                    Working...
                    X