Google Releases Chrome 96 With Back-Forward Cache Enabled For The Desktop

[Charlie68]

Hardware acceleration for video now also works under native wayland. Obviously the flag is needed :
--enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features=VaapiVideoDecoder

[Charlie68]

Native wayland support looks good now, I've been using it for days on Plasma wayland and so far I haven't had any problems.

[ⲣⲂaggins]

Doesn't Chrome use enough RAM already? On second thoughts, this feature is probably worth the extra memory cost.

[yump]

Firefox has had a bfcache practically forever, but it's disabled on a large fraction of websites because Mozilla made the unfortunate decision to respect the webdev's "cache-control: no-store" header more than the user's time and DOM state. And even that's an improvement from before, when it was disabled on all https:// pages.

So a whole lot of people have been trained to middle click everything anyway, because the back button often has huge UI latency and possible loss of form contents or lazy-loaded page elements.

[LinAGKar]

Lol, my literal first thought was "It didn't do that already? Huh. Well I'll be damned."

So I went down the rabbit hole and they're copying a Firefox feature from 2005.

So Firefox has had this for literally as long as I've been using the web. I thought this was just a standard thing in all browsers, I'm surprised Chrome didn't have it.

Firefox feature? Opera had that feature a couple of years before Firefox.

I guess it lost it when they moved to Chromium.

This feature is actually in support of a new DNS record type which tells the browser which protocol and protocol version to use. It doesn't matter which manner the new record is resolved, only that the record exists on the server.

I see. The article said it applied when the records were served over HTTPS, but it looks like he's removed that now.

[Vistaus]

And SeaMonkey (old Mozilla Suite / Netscape Navigator) have had this for more or less the beginning of Internet

Netscape was founded in 1994 as Mosaic, but it didn't have the back-forward cache back then. Opera introduced that feature in 1995 or 1996, shortly after it was first released. Netscape introduced that feature in 1997 because unlike Opera (which was a commercial browser back then), they were facing competition from the also free-released IE and needed to have something to stand out (which ultimately failed).

Opera introduced a lot of features back then that we now take for granted, including said back-forward cache.

[waxhead]

Firefox feature? Opera had that feature a couple of years before Firefox.

And SeaMonkey (old Mozilla Suite / Netscape Navigator) have had this for more or less the beginning of Internet

[Vistaus]

Lol, my literal first thought was "It didn't do that already? Huh. Well I'll be damned."

So I went down the rabbit hole and they're copying a Firefox feature from 2005.

Firefox feature? Opera had that feature a couple of years before Firefox.

[Frenzie]

So I went down the rabbit hole and they're copying a Firefox feature from 2005.

Opera did that since at least version 7 (2003).

[zamadatix]

An automatic HTTP to HTTPS redirect when hitting HTTPS DNS records. Basically if the DNS records are via HTTPS, assume the website is also accessible via HTTPS and use that by default.

This feature is actually in support of a new DNS record type which tells the browser which protocol and protocol version to use. It doesn't matter which manner the new record is resolved, only that the record exists on the server.