> Because more and more things are being built as SPAs on frontend with JavaScript Regarding not making the back button do anything in certain cases, I think p

> Because more and more things are being built as SPAs on frontend with JavaScript Regarding not making the back button do anything in certain cases, I think part of the problem is the shitty infinite-scroll, endless toilet-paper UX that many modern apps use for pagination. It makes a lot of UX choices awkward. Say you're building some Instagram or Pinterest type of App and you just have some kind of endless scroll to view content continuously. The user scrolls for 10 minutes seeing 100 pages worth of content on one root URL, and then clicks on another page and then goes back. What then? Do you put them at the bottom of the 100 pages on the original page after they hit that back button? It's not super difficult to save say the last item you scrolled to and go back there when you reload the page from a back button press, but that specific UX just makes it awkward to know where you even are within a specific page. Maybe if people get lost when going backwards and that's the UX choice, it's not even worth bothering.