Edit: so I just looked and it turns out you can enable tab bar scrolling on chrome://flags/#scrollable-tabstrip. Why is that even disabled by default?
It's my understanding that on mobile, tabs are unloaded from memory nearly instantly. You lose state but they use almost no resources. (I wish this was an option out of the box on Desktop. I've had extensions that do this and it's a godsend)
It's not that my phone was memory-constrained, we're talking a recent Samsung Galaxy flagship[3] - it's purely overly aggressive memory management on part of Firefox.
--
[0] - Have 5 tabs open, all something trivial like HN, put away phone, grab it 5 minutes later, switch to other HN tab, ... wait half a minute for it to reload on a spotty connection at my in-laws' countryside home.
[1] - Talking with others about how we experience technology, I'm starting to feel that I'm abnormally annoyed by large or unpredictable UI latency.
[2] - TypingMind.
[3] - I learned to save up and only buy high-end, thanks to the experience with my first smartphone, that turned out to be underspecced for its own functionality. It's probably a case of [1], but one time I deviated from this rule and got my wife a mid-range phone, we both started to regret it in a few months, so it's not only me who has low tolerance for jank.