[jschuur]

Discarding inactive tabs is not what I use The Great Suspender for. I use it to... suspend tabs. Auto Tab Discard doesn't seem to do that.

[fudged71]

What is the difference?

From the website it sounds like the favicon is changed. So the tab doesn’t go away it’s just on pause

Google: “ a discarded tab doesn't go anywhere. We kill it but it's still visible on the Chrome tab strip. If you navigate back to a tab that's been discarded, it'll reload when clicked. Form content, scroll position and so on are saved and restored the same way they would be during forward/backward tab navigation.”

In the future this will be updated to also use a serializer for discarded tabs.

[kchr]

Discard doesn't mean "remove" in this context. It will unload the tab, but still keep the state for when you switch back to it. E.g. suspend it.

[shawnz]

Discarding the tab is superior to what Great Suspender used to do. Why would you want the old behaviour?

Tab discarding is just a more efficient, native implementation of what Great Suspender aimed to do in the first place.

[Arnavion]

I don't use Chrome so I have no idea what either of these extensions did, but FF's implementation of tab discarding causes it to reload the page when I switch to the tab, which means I have to wait for the page to load before I can do whatever I wanted to do.

I'd much rather have a way to just stop all JS on a "suspended" tab so that FF doesn't burn 20% CPU on tabs that aren't even visible. (Yes I'm aware that JS timers, etc operate at reduced frequency for unfocused tabs. I'm talking about stopping them entirely.) Discarding may be more efficient for the browser but it's less efficient for me the user, so I don't use it.

[loceng]

Ah damn, I was about to try it to see if it actually discarded or suspended tabs.