> I've lost more data to that than any web browser bug over the years.

Is the back that backspace goes back, or that the browser doesn't store text you've typed in a textarea?

The browser does store the text in the text area, but the text area disappears when you reload the page because you need to click a button that adds that element to the page.

Well that's the page's fault, we used to call that "breaking the back button / history". And apparently not enough people think that was big enough of a deal to stop doing it. Unfortunately.

And even Opera tried to keep that too, at least in many situations, to keep the history an actual history and you'd switch through snapshots of the DOM+state--at least that's what it felt like, I'm not sure that's what it really did, but I guess it helps with speed, too. A webpage generally isn't supposed to move or change at all unless you're interacting with it, so really after it's rendered, flipping through history or tabs should be instant, even on an old machine because it's just bitmaps, really. I remember a while ago there was an article here that sort of explained why this couldn't be done or didn't work for some reason, but it was a tradeoff to get some feature that, given the option no one in their right mind would trade for instant history and tab navigation.

Even if it's the page's fault, you still lose your text. At that point, you don't really care who to get angry at, do you? Which is why I always disable backspace for back navigation.

The old Opera rarely had this problem, it would usually cache the input text. So if you accidentally went 'backspace' or closed the tab entirely you could easily recover your data in most scenarios. One could argue it's the user's fault for losing data, because using a sub-par browser is a choice. Just my 2 cents.

What browser you're using is not always a choice, or your choice is limited. In the workplace many users do not have local admin or the ability to install arbitrary browsers.