3 ms·
Maybe slightly off-topic, but the tutorial page adds entries to my (Firefox) back button as I scroll down. So when I tried to "back" to HN, nothing happened. Se
by ifdefdebug 11y ago
Maybe slightly off-topic, but the tutorial page adds entries to my (Firefox) back button as I scroll down. So when I tried to "back" to HN, nothing happened. Second, third back, nothing happened. Opening the back list, a dozen or so entries and they all do nothing.
I think this kind of design should really be avoided, it breaks my user experience.
- bbarn 11y agoYeah, I'm really getting tired of this "You just changed pages and didn't know it" pattern I'm seeing more and more. I'm not sure why people want to have this single page app at all costs, but if you want the single page app, than a single click of "back" should work.
- BinaryIdiot 11y agoI think there is value in doing single page apps but mostly for web applications not really for just a website. Still I completely agree that breaking the back button needs to be avoided.
- azernik 11y agoI think a more useful distinction is - mess with back-button history if and only if the user perceives a page transition regardless of if the location bar changed it there was a page load.
- jmkni 11y agoWaow that sucks, they don't even update the URL with anchor links!
- radnor 11y agoIt's a bug with JSBin and/or the browser. https://github.com/jsbin/jsbin/issues/2464 https://github.com/jsbin/jsbin/issues/2464
- pkhagah 11y agoNot really justifying history modification. But, if don't know, you can long click back button and press some random page in history stack to go to.